8.3: Rsync tasks, spaces in path problem

[mcel90]

Hi,

I have set up two freenas servers, both running 8.3.0-RELEASE-p1-x86. I have also set up a Rsync task over ssh (in system>Rsync Tasks) to backup files from one to the other using the steps described in the 8.3.0 users guide.

Whenever I enter a (local) path that contains spacing, Rsync gives an error during syncing that it cannot find the given path:

Code:

path: /mnt/data/backup/new folder
error: Dec 18 22:25:00 freenas rsync: lockf: folder: No such file or directory

If I remove the space from the foldername it syncs just fine:

Code:

path: /mnt/data/backup/newfolder
error: -none-

I've tried putting the path in single and double quotes but this is not seen as a valid path by the GUI:

Code:

path: 
'/mnt/data/backup/new folder'
"/mnt/data/backup/new folder"
GUI error:
The path must reside within a volume mount point

Also tried escaping the space with a \, still no success:

Code:

path: 
/mnt/data/backup/new\ folder
/mnt/data/backup/new\folder

error: 
Dec 18 22:34:00 freenas rsync: rsync: link_stat "/mnt/data/backup/new\ folder" failed: No such file or directory (2)
Dec 18 22:34:00 freenas rsync: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1053) [sender=3.0.9]

I found one other record of someone that seems to have a similar problem, no solution/ticket yet:
http://forums.freenas.org/showthread.php?9497-RSYNC-task-broken-after-upgrade

Can anyone else verify/replicate this behavior?

 

[William Grzybowski]

This issue has been fixed in r12947 and will be available in upcoming 8.3.1

 

[mcel90]

Awesome, thanks :)

 

[Eric Batte]

Is this still a problem in 9.10? I'm unable to successfully configure an rsync task with a remote path containing a space.

Error give in the UI is:

• The Remote Path you specified does not exist or is not a directory.
  Either create one yourself on the remote machine or uncheck the
  'rsync_validate_rpath' field.
  **Note**: This could also happen if the remote path entered
  exceeded 255 characters and was truncated, please restrict it to
  255. Or it could also be that your SSH credentials (remote host,etc) are wrong.