The Samba-Bugzilla – Bug 8849
Windows 7 SP1 Ultimate doesn't see directory changes (new files in directory)
Last modified: 2013-07-17 20:50:35 UTC
Created attachment 7438 [details]
Capture of SMB2 protocol when client doesn't see directory changes.
I have samba 3.6.3 server with rather standard config and enabled SMB2.
Windows 7 SP1 Ultimate x64 maps (mounts) share exported by this server.
Sometimes Windows 7 doesn't see changes in directories on this share. Only creating new file in directory by client itself or unmap/map share helps.
Attached capture contains part of such session.
Directory in question is:
Server IPv6 address is 2001:470:923f:1:21e:8cff:fe75:30d
Client IPv6 address is 2001:470:923f:1:95f3:701b:ec67:2bf4
(1) File "build.log" was created by server.
(2) Client doesn't see this file in FAR file manager and explorer.
(3) Capture is stared with "tcpdump" on server.
(4) Directory view is refreshed on client both in FAR file manager (Ctrl+R shortcut) and in Explorer ("Refresh" from context menu), Explorer window is closed and open again.
(5) File "touched.txt" is created with "touch" command from FAR file mmanager on client.
(6) Client shows both "build.log" and new "touched.txt" files.
Does the client see files that were created by other cifs clients?
(In reply to comment #1)
> Does the client see files that were created by other cifs clients?
Yep, it helps too. "stale" client sees both of them almost instantaneously, and it fix situation for some time (files, created on server shows up on client without any additional actions). But not for long :(
Maybe, it is not exactly samba bug, but Windows 7 bug, as here are long-standing reports, that people have same problem with W2K8R2 server:
And now, "new" client, which helps stale one by creating file, stalls itself, and doesn't see any new files till first client creates one new via CIFS.
Are those new clients Windows 7 as well or they are Samba clients?
(In reply to comment #5)
> Are those new clients Windows 7 as well or they are Samba clients?
All of them are Win'7 clients. I'll try with only WinXP client I have, next time problem occurs (I hope, in couple of hours).
Creating file by WinXP (not SMB2-capble) client helps too. WinXP client doesn't have any problems to "notice" new files, created by server itself without any additional actions, too.
And more: if Win7 client "stick" to some view of directory, it could be deleted completely and re-created with new content on server, but client will "see" old content (of directory) and shows errors on any attempt to open files from it.
a dup of bug 9935 ?