similar to: Samba and macOS questions

Hi all, We use the vfs_fruit module and lately we have experienced that random files copied with Finder are being grayed out. We think this is probably due to the extended attribute "user.DosStream.AFP_AfpInfo:$DATA" not being updated/removed after the file is copied. If we manually remove the xattr in question with the command setfattr -d 'user.DosStream.AFP_AfpInfo:$DATA', the

Hi I apt installed Samba Version 4.9.5-Debian (latest in their repos) on a fresh-built Raspbian Buster Lite release 2020-02-05. I put together the configuration outlined below by using the docs at https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X and https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html. The underlying usb hard drive is an ext4 partition

I notice the Configure Samba to Work Better with Mac OS X has been radically shortened?not sure why, but you may want to look at my original 22 Apr 2019 version in the history. You may want to put vfs objects in Global. Note in the vfs_fruit man page: Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate SMB2 AAPL protocol extensions on the first tcon, so mixing shares

(example: Configure Samba to Work Better with Mac OS X [ https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X] ). Thanks for the suggestion though. I've now been trying out the various Apple specific flags in vfs_fruit ( https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html), though with no success thus far. Example settings tried in smb.conf: [global]

In case of FreeBSD, the name of the extended attribute is wrong. % lsextattr user ICONandEA.txt ICONandEA.txt netatalk.Metadata com.apple.TextEncoding com.apple.metadata:kMDItemFinderComment "netatalk.Metadata" is incompatible to Netatalk. The first atom "org." is removed. source3/include/smb.h: /* Prefix for DosStreams in the vfs_streams_xattr module */ #define

Mon, 28 Dec 2015 18:24:17 +0100, Ralph Boehme <slow at samba.org>: > On Tue, Dec 29, 2015 at 01:34:34AM +0900, HAT wrote: >> In case of OS X 10.9 and later, any file could not be removed. >> >> $ rm test.txt >> rm: test.txt: Resource busy >> >> cannot remove: >> OS X 10.11.2 El Capitan >> OS X 10.10.5 Yosemite >> OS X 10.9.5

Hello Kevin, Mac OS by default looks for TimeMachine volumes over AFP not CIFS-SMB… Like you, I experimented with Samba a couple of years ago to try to get it to work anyway. With a few modifications on the client’s part and some configuration on the Samba server I got it to work… but recovery only worked for clients that I had configured in advance… Recovery with the Mac OS tools (Migration

I worked with Netatalk for years and want to switch to Samba now. Currently i use Ubuntu 20.04. and Debian 9 before, i had no issues with netatalk at all. As soon as i try to add a color tag (e.g. yellow) with Mac OS 10.15.5, the tag appears shortly but hides one second later. The file system is ZFS with no special options configured. I tried the Ubuntu package but also the builds from source

On 26/12/15 17:33, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: >> On 26/12/15 17:08, HAT wrote: >>> Hi, >>> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. >>> >>> The EAs are not seen from clients yet. >>> >>> smb.conf: >>> path = /export/test1/ >>>

Is it possible to backup Mac OS devices through a Samba share on Samba 4.4.6 on Fedora 24 with Time Machine? I am able to successfully advertise the share through Avahi, connect to it in Finder, and read/write files. I am also able to see the share as a destination in Time Machine, but selecting it shows an error that "The selected network backup disk does not support the required

Hi HAT! Nice to meet you over here... ;) On Wed, Mar 11, 2015 at 11:30:45PM +0900, HAT wrote: > Hi. > I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. > I confirmed that ResourceFork and FinderInfo are compatible with > Netatalk 3.1.7. However, EAs are incompatible. > The character ":" in EA name is wrong. > The EAs are not seen from clients. >

Hi. I'm testing samba 4.2.0 vfs_fruit on Fedora Server 22-alpha. I confirmed that ResourceFork and FinderInfo are compatible with Netatalk 3.1.7. However, EAs are incompatible. The character ":" in EA name is wrong. The EAs are not seen from clients. smb.conf: [test2] path = /export/test2 writable = yes vfs objects = catia fruit streams_xattr fruit:locking =

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

On 26/12/15 17:08, HAT wrote: > Hi, > I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > > The EAs are not seen from clients yet. > > smb.conf: > path = /export/test1/ > writable = yes > vfs objects = catia fruit streams_xattr > fruit:locking = netatalk > fruit:encoding = native > streams_xattr:prefix = user.

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

On Mon, Apr 03, 2017 at 03:46:49PM +0200, Frank Heldt via samba wrote: > Hello all, > > I’m trying to use samba 4.5.8 as a file server for my Macs (all 10.12.4 now), as a replacement for netatalk. > > I did setup smb.conf as suggested > > # > # Options for macOS > # http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS

> Please keep the wiki page simple. Anyone who wants to get > down and dirty > has to read man vfs_fruit and understand what the options are > really for > and he probably also has to understand the code. Its not about getting down and dirty, but about gettings a simple setup for samba version X.YY for users that are more beginners. And exactly my point a beginner, will fail,

On Sun, Dec 27, 2015 at 02:33:10AM +0900, HAT wrote: > Sat, 26 Dec 2015 17:22:56 +0000, Rowland penny <rpenny at samba.org>: > > On 26/12/15 17:08, HAT wrote: > >> Hi, > >> I'm testing samba 4.3.3 vfs_fruit on Fedora rawhide. > >> > >> The EAs are not seen from clients yet. > >> > >> smb.conf: > >> path =

Yes, I've tried all of them at this point. I spent some time focusing on SMB2 due to various sources indicating they target it for stability (example: Configure Samba to Work Better with Mac OS X [ https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X] ). Thanks for the suggestion though. I've now been trying out the various Apple specific flags in vfs_fruit (

Hello all, I’m trying to use samba 4.5.8 as a file server for my Macs (all 10.12.4 now), as a replacement for netatalk. I did setup smb.conf as suggested # # Options for macOS # http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS <http://netatalk.sourceforge.net/wiki/index.php/Netatalk_3.1.11_SRPM_for_Fedora_and_CentOS> # ea support = yes vfs