NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
lemon8
Mar 18, 2012Aspirant
RSYNC: Invalid filenames = stuck files
I'm backing up from a MacBook Pro to ReadyNAS Pro Business using FrontView's backup scheduler and RSYNC. Using User-level access but I don't have any users configured. All shares, including my backu...
lemon8
Mar 19, 2012Aspirant
Just wanted to post a followup to say that the filenames in question are actually named with colons in their filenames (:)
Mac OS APIs translate between colon and forward slash. In the Finder you can use a forward slash in a filename and it gets transparently written to disk as a colon. If you specify a colon it will change over to a slash in finder and remain as a colon on disk.
Any such files or folders will be inaccessible on the ReadyNAS if created there by RSYNC. The only way I've managed to recover is to trash the entire share. Unfortunately a number of Apple-provided (and I supposed some third-party) programs will use slashes in filenames and rely on the file creation APIs to translate. This means there end up being a lot of files that can cause these issues. Thankfully I'm not planning to back any of these paths up and have restrictedly RSYNC backups to my Documents and Images folder hierarchies.
I've done a search for any offending files and have corrected the three I found to remove the colons. Now the only problem remaining is accented characters.
Mac OS APIs translate between colon and forward slash. In the Finder you can use a forward slash in a filename and it gets transparently written to disk as a colon. If you specify a colon it will change over to a slash in finder and remain as a colon on disk.
Any such files or folders will be inaccessible on the ReadyNAS if created there by RSYNC. The only way I've managed to recover is to trash the entire share. Unfortunately a number of Apple-provided (and I supposed some third-party) programs will use slashes in filenames and rely on the file creation APIs to translate. This means there end up being a lot of files that can cause these issues. Thankfully I'm not planning to back any of these paths up and have restrictedly RSYNC backups to my Documents and Images folder hierarchies.
I've done a search for any offending files and have corrected the three I found to remove the colons. Now the only problem remaining is accented characters.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!