Does the CreateDisposition flag of a client depend on Server's response ?

varun mittal vmittal05 at gmail.com
Fri Feb 3 15:21:57 UTC 2023


I was able to narrow it down to the "Named Streams" bit in
"FileFSAttributeInformation" response.
When this value is toggled from 0 to 1, as is advertised by `streams_xattr`
VFS module, Robocopy
switched from FILE_OPEN to FILE_OPEN_IF.

Thanks

On Mon, Jan 30, 2023 at 1:33 AM varun mittal <vmittal05 at gmail.com> wrote:

> I made some progress on this.
> It seems the `streams_xattr` VFS module is making the difference.
>
> On Samba-4.9.5-Debian, which was not working earlier,
> once I disable this module Robocopy changes the CreateDisposition flag
> and it starts working. But I could not spot the difference in traces
> https://tinyurl.com/robocopy-issue
>
>
> On Sat, Jan 28, 2023 at 1:33 AM Jeremy Allison <jra at samba.org> wrote:
>
>> On Sat, Jan 28, 2023 at 01:27:36AM +0530, varun mittal wrote:
>> >   > Wireshark will be the key. Compare between Windows server and Samba.
>> >   That is what I thought and have started looking. Any suggestions on
>> which
>> >   call in particular, there are so many :)
>> >   BTW, with a Windows server, the flag is FILE_OPEN_IF
>>
>> Well that's at the point you know there's a difference,
>> so work back from that point. Try bisecting the trace
>> to see where it starts to diverge. No tools for that
>> so you'll have to do it by hand (something I unfortunately
>> have great experience with :-).
>>
>


More information about the samba-technical mailing list