And although it creates directory, it doesn't copy contents, because it stops
process of copying directory after this error. If I repeat filesync, the
contents of directory will be copid (cause directory is already here).
So, it looks exactly the same.
If so, then problem in chflags().
I expect that samba on linux is compiled without support for chflags, obviously.
I presume that settings "unix extensions = no" would probably fix this, but it
has a drawback, because then you loose native unix things like symlinks etc.
Which is, at least in our case is not possible, cause shares accessed by both,
mac and linux clients over NFS (the same clients on different hosts) and
symlinks are heavily used.
I think, OSX client, when it sees that server supports "unix extensions",
expects that on other side is OSX server with samba which supports chflags.
So, if we don't discuss rewrite of OSX cifs FS, then only solution is to
"emulate" chflags support on samba side (or convert flags to XFS/ETX3 attrs
somehow)
On Dec 16, 2009, at 6:48 PM, Anton Starikov wrote:
> Probably it can be related.
>
>
> In my case filesync of portable directories with samba server always fail for
> newly created directories with error
>
> 0:: 09/12/16 06:49:55.282 EXCEPTION: Invalid argument <-SStoreFileOperator_FS
> applyPermissionsFromObject: (StoreFileOperator-FS.m:508):
> chflags('/Network/Servers/samba.server.host/cifstest/', flags=0)--> Error
> Domain=NSPOSIXErrorDomain Code=22 UserInfo=0x10058c170 "Invalid argument">
>
> It tries to chflags after creation of directory and get this error.
>
> Anton.
>
>
>
> On Dec 16, 2009, at 6:37 PM, Ryan Suarez wrote:
>
>> Volker Lendecke wrote:
>>> On Wed, Dec 16, 2009 at 09:30:18AM -0800, Jeremy Allison wrote:
>>>
>>>>> Yes, I have seen this at a customer site. I've stared at the
>>>>> logs and sniffs for MANY hours, but I could not find
>>>>> anything. If you solve this, please let me know :-)
>>>>>
>>>> Try pinging George and James (CC:ed on this :-).
>>>>
>>>> Hopefully they can help.
>>>>
>>>
>>> Already done. Jht mentioned that turning off winbind fixed
>>> it for him ... :-)
>>>
>> hmm, this server isn't even running winbind...
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
