Hi.

 

I would like to allow ._* files on one share as when rsyncing to it for dackups files starting with an undrescore do not get copied as the temporary file that rsync tries to make gets blocked, and there are some libraries I use that have files with _ as their first character.

 

What is the best way to allow this in unraid? I have another server that doesn't block these but I have been testing unraid for my backup server.

 

Thanks.

I have worked out that if I remove vfs objects fruit and streams_xattr it then works. But I need that for other shares. Can I make custom changs to this share somehow? 

Related question, what would putting the entire share config in smb-extra.conf instead do?

Here is the contents of smb.conf
 

# configurable identification
        include = /etc/samba/smb-names.conf

        # log stuff only to syslog
        logging = syslog@0

        # we don't do printers
        show add printer wizard = No
        disable spoolss = Yes
        load printers = No
        printing = bsd
        printcap name = /dev/null

        # misc.
        invalid users = root
        unix extensions = No
        wide links = Yes
        use sendfile = Yes
        aio read size = 0
        aio write size = 4096
        # supposedly not needed anymore
        #allocation roundup size = 4096

        # ease upgrades from Samba 3.6
        acl allow execute always = Yes
        # permit NTLMv1 authentication
        ntlm auth = Yes

        # hook for user-defined samba config
        include = /boot/config/smb-extra.conf

        # auto-configured shares
        include = /etc/samba/smb-shares.conf

As you can see, the smb-shares.conf will execute after smb-extra.conf so any conflicting settings in smb-shares.conf will have precedence on those in smb-extras.conf.

I think rsync will create a destination file with same name as source file but prepends a '.' to the file name to make it "hidden". Then when transfer completes it performs a 'rename', thereby deleting previous copy of source file, replacing it with new copy.  I think if you can use the '--inplace' option it doesn't do this, instead it opens destination for write which deletes old file and new data is written to the file.

I am not 100% sure I can modify the rsync commands as they are built into BackInTime but I will have a go and see if this is possible. It might be a configurable flag somewhere.

 

Otherwise doing the manual edit isn't a massive trauma as I don't reboot the server much anyway.

Just to update this, there is an option to put --inplace in the rsync command used by backintime, I am testing to see how it works.