Bug 8849 - Windows 7 SP1 Ultimate doesn't see directory changes (new files in directory)
Windows 7 SP1 Ultimate doesn't see directory changes (new files in directory)
Status: NEW
Product: Samba 3.6
Classification: Unclassified
Component: SMB2
3.6.3
x64 FreeBSD
: P5 normal
: ---
Assigned To: Jeremy Allison
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-07 21:53 UTC by Lev Serebryakov
Modified: 2013-07-17 20:50 UTC (History)
1 user (show)

See Also:


Attachments
Capture of SMB2 protocol when client doesn't see directory changes. (14.73 KB, application/x-bzip2)
2012-04-07 21:53 UTC, Lev Serebryakov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lev Serebryakov 2012-04-07 21:53:45 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:

/usr/home/lev/FreeBSD-commiter/ports/devel/msp430-gcc
Z:\FreeBSD-commiter\ports\devel\msp430-gcc

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.
Comment 1 Volker Lendecke 2012-04-08 08:03:57 UTC
Does the client see files that were created by other cifs clients?
Comment 2 Lev Serebryakov 2012-04-08 11:05:04 UTC
(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 :(
Comment 3 Lev Serebryakov 2012-04-08 11:06:29 UTC
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:

http://social.technet.microsoft.com/Forums/bg-BG/w7itprogeneral/thread/947489ae-dc86-45f0-ad5e-463a62e1d59f
Comment 4 Lev Serebryakov 2012-04-08 11:07:40 UTC
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.
Comment 5 Alexander Bokovoy 2012-04-08 11:58:41 UTC
Are those new clients Windows 7 as well or they are Samba clients?
Comment 6 Lev Serebryakov 2012-04-08 12:09:33 UTC
(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).
Comment 7 Lev Serebryakov 2012-04-08 12:24:57 UTC
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.
Comment 8 Björn Jacke 2013-07-17 20:50:35 UTC
a dup of bug 9935 ?