----- Original Message ----- > From: "David Morrison" <davidmorrisonl...@gmail.com>
>>\In fact, no -- while I am not The Man, it seems to me that at that point, >>you have to worry about the *internals* of the filesystem, since the block >>offsets are going to change, and the inodes must then also change. >> >>It would seem to boost the complexity a *lot*, from my viewpoint. > > I agree. I would add further that if you have a failing mechanism, > the last thing you want to be doing is reading the whole disk, saving > some parts, then presumably later reading the disk again to get the > good blocks. You could have extra bad blocks by then which would > leave you no better off. Wait: he meant "read the bad blocks into a file, and then *overlay them on the mounted dying drive*"?? Oh ghod no; that's a non-starter. Cheers, -- jra -- Jay R. Ashworth Baylink j...@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274 _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue
