-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Jun 12, 2005 at 03:45:19AM +0200, Dag Wieers wrote: > > Check my other post regarding this. Dump won't clone wholedisks. It > > will clone filesystems (with all metadata intact). > > The problem with a broken disk is that your filesystem may not be correct. > And you can't do a fsck to correct the inconsistencies because the disk is > not reliable. > > That's why you require something like ddrescue, so you can copy everything > that is still accessible and fill the blank spaces in with zero-blocks. > So it doesn't abort or truncate the output like dd, maybe dd conv=noerror > is similar but ddrescue has other features like proper status info during > copying and decreasing blocksize when blocks fail to be read. I never tried ddrescue, so I can't comment. But, as far as I remember, dump will only abort if you get an error on the writing side. Memory can be at fault here, tho. - -- Rodrigo Barbosa <rodrigob at suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCrJLTpdyWzQ5b5ckRAuvFAJ9VjR06v6sm2LMI/MNppBOjbNl5lwCffL69 fYeSQINkwkAkvmy08E7IpuQ= =mB2T -----END PGP SIGNATURE-----