Thanks, Harald. With your input I was able to put together a pretty
easy solution to this problem, specifically use "*.foo*" instead of
"*.foo" as rsync's temp file names are in the format of <original-file-
name.ext>.XXXXX where XXXXX is random. I think I saw this mentioned
here before but forgot about it until now.
Thanks!
Dan Parsons
On Jan 13, 2009, at 9:12 PM, Harald Stürzebecher wrote:
2009/1/14 Dan Parsons <dparsons@xxxxxxxx>:
I'm copying data back to my newly rebuilt glusterfs, and one of the
things
I'm doing is using unify with the switch scheduler to send certain
file
extensions to a stripe volume and others to a dht volume.
When using rsync to restore this data, all files are going to dht
(which I
do not want). When I use cp, the correct file extensions go to
stripe, and
the others go to dht.
What's special about rsync that's causing this problem? Is there
any way
around this?
IIRC, rsync (with default settings) creates temporary files in the
target directory and renames them after the download is complete.
As these temporary files probably don't have the same extension as the
real file the switch scheduler will not be able to choose the correct
volume.
http://www.samba.org/ftp/rsync/rsync.html says that rsync has some
options to control temporary files and file creation:
-T, --temp-dir=DIR create temporary files in directory DIR
--inplace
Anything that forces rsync to create the file with its real name
should help with your problem, but might have side effects.
Harald Stürzebecher
