Fwd: SMB2 not respecting mtime values
jshivers at redhat.com
Thu Jan 24 17:24:53 UTC 2019
On Thu, Jan 24, 2019 at 12:11 PM Ralph Böhme via samba-technical
<samba-technical at lists.samba.org> wrote:
> On Thu, Jan 24, 2019 at 09:03:41AM -0800, Jeremy Allison via samba-technical wrote:
> >Maybe. Changing meta-data semantics on write is fraught with danger,
> >and we don't even do that for SMB1 unix extensions. So let's not
> >add contraints we don't understand yet please.
> >My money is on a client bug, as always :-).
> fwiw, just in case you were not aware of this one:
> We also seem to have a bug that a set-eof on a handle with
> set-eof-size=existing-size doesn't flush a pending write time update. At least
> newer Windows server seem to do that.
This seems like what the issue is.
The SMB server is uptime mtime after the server actually flushes to
Both Samba and Windows SMB servers accept the SETINFO where the
nanosecond timestamps are being set.
By all accounts the servers are telling the client that the attributes
the client is trying to set are accepted.
This seems more like an issue with implementing the protocol or with
the protocol itself.
Copying the same file to a SMBv1.0 file share from a Windows SMB
server, which doesn't have posix extensions, yields the same results
as copying to a Samba server.
I am copying a packet capture from a Fedora rawhide system to a
Windows 2016 system using SMBv2.1 and SMBv1.0. I used 2.1, but the
same behavior can be observed with SMB3.x
I have used different versions of Samba, but is there a preferred
version that anyone would like used for testing?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 32316 bytes
Desc: not available
More information about the samba-technical