Messages in this thread | | | Date | Thu, 6 Nov 2003 12:22:39 -0500 | From | Theodore Ts'o <> | Subject | Re: undo an mke2fs !! |
| |
On Thu, Nov 06, 2003 at 04:01:48PM +0100, Pavel Machek wrote: > Hi! > > > If you had backed up the metadata using an e2image command, you would > > have been fine, but that command takes a while to run, so most people > > don't bother to do this. (Not a bad idea for the absolute paranoids > > in the house would be to run e2image out of a cron script and save the > > image file on some *other* filesystem.) > > Assuming I have e2image (I'm actually started to thinking it is pretty > good idea)... how do I restore it?
<Blush> The libext2fs library routines are there, but the userspace tools haven't been written yet. What I've done the few times when I've used it is to let debugfs access the image file, and use it mostly for examination purposes.
What I'll probably do is add debugfs commands that allow you to copy the superblock/block group descriptors, or the inode table, or the block/inode allocation bitmaps from the image file back to the filesystem. As I said, the library routines are there, but debugfs front ends haven't been written yet. If someone has a critical situation requiring them, I could probably throw together patches within a day or so.
- Ted
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |