Macos – Rsync fails for files that start with underscore when destination is zfs

backupcommand linemacosrsynczfs

I'm using rsync3.1.0pre1 on Mac OS X 10.8.5, and am trying to rsync one folder to another. The destination is a ZFS volume mounted via SMB.

The problem I'm having is that files that start with underscore (e.g., '_filename.jpg') are not being successfully synced to the destination. I get the following error message:

rsync: mkstemp "/path/to/destination/._filename.jpg.NUgYJw" failed: Permission denied (13)

In this case, _filename.jpg does not make it to the destination.

I understand that rsync creates hidden, temporary files at the destination which are preceded with . and have a random file extension appended on the end. But the original filename starts with _, not ._, and I haven't asked rsync to copy extended attributes / resource forks over (unless it always does it).

The rsync command I'm using is:

rsync -av --exclude='.DS_Store' --exclude '.Trash' --exclude 'Thumbs.db' --exclude '._*' --delete /source/ /destination/

Has anyone found a way around this problem? Thank you!

Best Answer

From the original poster, question revision 3:

We found the answer (Dave Veffer did). The smb server was vetoing ._*. Simply had to remove that from smb.conf. I'm using SMBUp on OS X. smb.conf is located at /opt/local/etc/samba3/smb.conf

Related Solutions

Windows – Options (–partial, –partial-dir) in rsync don’t work as I would expect

I was launching this command from the Windows Task Scheduler. When I took the command and ran it from a console (command prompt), the options worked as they should*.

The only difference between the execution of the commands happened when I tried to end them. In the console, pressing Ctrl+C, rsync ended with the error

rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at ...

In the Windows Task Scheduler, right-clicking the running task and selecting End resulted in the error

rsync: read error: Connection reset by peer (104)

So, I can only assume that the way the Windows Task Scheduler ends a process differs from the way rsync expects to end*, and this makes rsync end without doing its exiting routines.

* - I found more about the way --partial and --partial-dir work.

With --partial, rsync creates a temporary file like I saw, but when rsync ends (in an expected way), it renames that temporary file to the regular filename (e.g. renames .[filename].2dxZ1a to [filename]) and then makes a copy of the partial file to a new temp file on the next run (e.g. copies [filename] to .[filename].34cae2).

With --partial-dir, rsync fills the temporary file, then on close, moves the temporary file into the directory you specify as the regular filename (e.g. renames .[filename].2dxZ1a to [partial-dir]/[filename]). Then, on the next run, it copies the file from [partial-dir] to a new temporary file in the destination directory.

Rsync synchronizing files only without creating folders on destination

Try the following:

rsync -av src:/dir/to/files/* /dest/dir

If you have multiple nested subdirectories, you'll need to do something like this first:

find /dir/to/files -type d -print

Run that list of directories through a loop and call rsync each time. Of course, assuming you're doing this on a remote machine, you'll need to issue the find via ssh and store the results in an array and then execute the rsync loop.

Related Question