On Thu, Feb 24, 2011 at 10:59:23AM +0200, Amir Goldstein wrote: > That tool is e2image -r, which creates a sparse file image of your > fs (only metadata is written, the rest is holes), so you need to be > careful when copying/transferring it to another machine to do it > wisely (i.e. bzip or dd directly to a new HDD) Not sure what you > will do if fsck fixes errors on that image... Mostly (if it didn't > clone multiply claimed blocks for example), you would be able to > write the fixed image back onto your original fs, but that would be > risky. I can then run the fsck tests on the image. I expect fsck to find errors: I'm using the filesystem when I'm making that image.... It won't be consistent. Roger. -- ** R.E.Wolff@xxxxxxxxxxxx ** http://www.BitWizard.nl/ ** +31-15-2600998 ** ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
