On 12/02 01:27 , Oliver Freyd wrote: > The pool is a reiserfs3 on LVM, about 300GB size, but with a lot of > hardlinks... > Now I'm trying to put the pool onto a new filesystem, so I created an > XFS on a striped RAID0 of 3 disks (to speed up copying), and use > rsync -aHv to copy everything including the hardlinks. > The cpool itself took about a day, and now it is running for 6 days and > maybe it has done 70% of the work. BTW, a copy with dd takes about 2 hours.
Yep. this is normal. you've discovered why backing up the BackupPC data pool with rsync is a non-scaleable solution. As you noted, dd is the way to go if at all possible. If you want to change the filesystem (i.e. make a file-level copy); best thing is to use tar. Presuming that your old data pool is under /var/lib/backuppc and the new filesystem is mounted on /mnt/newfilesystem: cd /var/lib/backuppc; tar cpf - . | tar xpv -C /mnt/newfilesystem Is the use of RAID0 on 3 disks a temporary thing? Keep in mind that the more disks you have the greater the likelihood that one of them will die. With RAID0 if one dies you lose all your data. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
