Hi, i'm running Samba 4.2.1 compiled from source on an Ubuntu 10.04.4 LTS Server. ACL/XATTR is active and working. I tried to activate the vfs_fruite module and added the sample code: vfs objects = catia fruit streams_xattr fruit:resource = file fruit:metadata = netatalk fruit:locking = netatalk fruit:encoding = native to the share. In addition i tried the following share definition: vfs objects = catia fruit streams_xattr fruit:locking = netatalk streams_xattr:prefix = user. streams_xattr:store_stream_type = no kernel oplocks = no The other definitions i use are: path=/path/to/share browseable=yes admin users = @filetest valid users = @filetest writable = yes guest ok = no force user = root force group = basegroup create mode = 0775 directory mode = 0775 It is not possible to write to the share at best at the first time i click on save. Sometimes i get 0 Byte files and with a plain text file the initial content is saved. Trying to save a file again results in an error that writing to the share isn't possible (resource busy says TextMate ...). When starting up Samba i see this error: Apr 25 12:09:28 SERVERNAME smbd[13730]: ? error reading meta xattr: Operation not supported Which is somehow funny as XATTR are definitely working, followed the instructions in the last past: http://ubuntuforums.org/showthread.php?t=2206240 Maybe this error could help resovle the issue: Apr 25 12:12:25 SERVERNAME smbd[13914]: [2015/04/25 12:12:25.841615, ?2] ../source3/modules/vfs_fruit.c:902(ad_header_read_rsrc) Apr 25 12:12:25 SERVERNAME smbd[13914]: ? Operation not supported: bad size: 0 I really hope Ralph B?hme could help here. Thanks, Christian
I must reply to my own post. Changing the fruit:locking to "none" results in a working share. Netatalk 3.1.6 is installed and from the information of the changelog Netatalk 3.1.7 doesn't change anything to the file locking (except if you're using Solaris). Am 25. April 2015 bei 12:16:20, Christian Kovacic, MA (chris.k at gmx.at) schrieb: Hi, i'm running Samba 4.2.1 compiled from source on an Ubuntu 10.04.4 LTS Server. ACL/XATTR is active and working. I tried to activate the vfs_fruite module and added the sample code: vfs objects = catia fruit streams_xattr fruit:resource = file fruit:metadata = netatalk fruit:locking = netatalk fruit:encoding = native to the share. In addition i tried the following share definition: vfs objects = catia fruit streams_xattr fruit:locking = netatalk streams_xattr:prefix = user. streams_xattr:store_stream_type = no kernel oplocks = no The other definitions i use are: path=/path/to/share browseable=yes admin users = @filetest valid users = @filetest writable = yes guest ok = no force user = root force group = basegroup create mode = 0775 directory mode = 0775 It is not possible to write to the share at best at the first time i click on save. Sometimes i get 0 Byte files and with a plain text file the initial content is saved. Trying to save a file again results in an error that writing to the share isn't possible (resource busy says TextMate ...). When starting up Samba i see this error: Apr 25 12:09:28 SERVERNAME smbd[13730]: ? error reading meta xattr: Operation not supported Which is somehow funny as XATTR are definitely working, followed the instructions in the last past: http://ubuntuforums.org/showthread.php?t=2206240 Maybe this error could help resovle the issue: Apr 25 12:12:25 SERVERNAME smbd[13914]: [2015/04/25 12:12:25.841615, ?2] ../source3/modules/vfs_fruit.c:902(ad_header_read_rsrc) Apr 25 12:12:25 SERVERNAME smbd[13914]: ? Operation not supported: bad size: 0 I really hope Ralph B?hme could help here. Thanks, Christian
On Sat, Apr 25, 2015 at 12:28:03PM +0200, Christian Kovacic, MA wrote:> I must reply to my own post. > > Changing the fruit:locking to "none" results in a working share.can you please file a descriptive bugreport that fruit:locking=netatalk seems to have a problem? Thanks! -Ralph -- SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de,mailto:kontakt at sernet.de