Newly created files not visible in Windows client without refresh

[gaaichan998]

After migrating from Samba to KSmbd using the same configuration file, I noticed that newly created files in the shared directory are not immediately visible in the Windows client. The files only appear after manually refreshing the file explorer (F5).

This behavior does not occur when using Samba with the same configuration file, where files appear instantly in the Windows client.

Environment

• KSmbd Version:

modinfo ksmbd
filename:       /lib/modules/6.1.0-28-amd64/kernel/fs/smb/server/ksmbd.ko
softdep:        pre: crc32
softdep:        pre: gcm
softdep:        pre: ccm
softdep:        pre: aead2
softdep:        pre: sha512
softdep:        pre: sha256
softdep:        pre: cmac
softdep:        pre: aes
softdep:        pre: nls
softdep:        pre: md5
softdep:        pre: hmac
softdep:        pre: ecb
license:        GPL
description:    Linux kernel CIFS/SMB SERVER
version:        3.4.2
author:         Namjae Jeon <linkinjeon@kernel.org>
srcversion:     B30925F9014A233760082C7
depends:        cifs_arc4
retpoline:      Y
intree:         Y
name:           ksmbd
vermagic:       6.1.0-28-amd64 SMP preempt mod_unload modversions
sig_id:         PKCS#7
signer:         Debian Secure Boot CA
sig_key:        32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43
sig_hashalgo:   sha256
signature:      76:75:26:B3:7F:A0:C5:04:83:B3:E4:81:47:6A:53:DE:C8:AC:B0:19:
                FB:F1:CB:F4:B8:8C:94:4F:BA:D4:45:B9:6B:30:6D:47:E7:79:BB:E5:
                02:F7:AE:1A:B6:6B:62:3D:C9:F7:A6:49:6B:5E:E1:90:4B:7F:F8:03:
                82:A6:11:33:3A:23:1D:B4:52:15:B7:A1:BF:14:F6:DC:DA:9E:69:07:
                08:B0:54:72:9A:4B:B0:D5:43:64:9F:67:AE:53:19:F1:72:BD:6C:85:
                9B:EE:94:92:08:CE:48:A8:DD:27:AB:CC:55:6F:D7:E0:A3:7C:4E:AE:
                39:11:3A:A5:E6:27:BD:8F:CF:BC:CA:47:AD:57:C2:A5:1E:FA:55:2C:
                46:0C:53:98:7A:A6:F7:E7:E7:13:C2:4C:18:24:1F:30:D4:F0:53:6D:
                78:64:00:D0:DB:2B:AD:72:D2:D5:92:DC:B3:39:F5:E1:BF:E7:02:D5:
                6F:43:C1:E7:59:97:02:1A:DF:48:79:2E:AF:87:38:AD:65:01:23:56:
                2B:E8:7D:AA:8D:78:D3:7A:E9:86:4F:F9:F9:63:1D:D5:0C:21:12:A4:
                27:64:3B:32:08:1F:71:91:F3:80:B3:D4:C1:E7:C3:D2:00:36:63:D3:
                C2:21:2D:3A:98:D8:D1:8E:3D:8D:9A:C5:14:49:9C:42

• ksmbd-tools version : 3.4.7
• Linux Distribution: Debian GNU/Linux 12 (bookworm)
• Kernel Version: Linux 6.1.0-28-amd64
• Windows Client Version:

Edition	Windows 10 Pro
Version	22H2
Installed on	‎5/‎22/‎2021
OS build	19045.5247
Experience	Windows Feature Experience Pack 1000.19060.1000.0

Config:

[global]
        max connections = 16384

[tf]
        path = /media/main
        read only = no
        create mask = 0644
        valid users = user

[namjaejeon]

It is normal. There is smb2 notify command in smb protocol. It is not implemented in ksmbd yet.