I want to be 100% sure I'm doing this correctly to avoid the user share copy bug. I'm moving data between disks to convert each disk to one of the new filesystems. I have 5 disks, all of which are included in two user shares. I recently added the 5th disk and I want to move the data off the 1st disk, using the command.

 

rsync --progress -avh /mnt/disk1/ /mnt/disk5/

 

Where I will then format disk1 and then repeat the process with disk2 -> disk1.

 

Am I doing this right?

Looks ok.

Thats exactly what I've been doing.

Yes, that's fine.  The bug is a user SHARE bug => as long as you're copying between disks and not using the share references, you're fine.

 

... one caveat, however ==> as you have hopefully already noticed, there's an issue with writing certain files to Reiser volumes in Beta's 7 & 8 ... so be sure you're either using an earlier version, or have upgraded to Beta 9 if you're doing these copies with v6.

 

... one caveat, however ==> as you have hopefully already noticed, there's an issue with writing certain files to Reiser volumes in Beta's 7 & 8 ... so be sure you're either using an earlier version, or have upgraded to Beta 9 if you're doing these copies with v6.

 

Yep made sure to upgrade to Beta 9 first. Thanks for the confirmation guys.

If you use the --remove-source-files it will remove them off the source drive after a successful copy...

 

Edit: only down side is you are updating parity twice for the new file and removal of the old, but I prefer the sanity of know the drive is empty before formating...

If you use the --remove-source-files it will remove them off the source drive after a successful copy...

 

Edit: only down side is you are updating parity twice for the new file and removal of the old, but I prefer the sanity of know the drive is empty before formating...

 

Oh yeah I thought about that, but I want this to go as fast as possible (without disabling the parity drive, just in case).

Does this command preserve the original file date?