Re: undo an mke2fs !!

[Pavel Machek <pavel@ucw.cz>]

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.
> > 
> > I guess I'll start recomending e2image to people trying software
> > suspend ;-). It really seems like neat tool for "easy backups".
> 
> Note that according to Ted's first post, e2image backs up the _metadata_. He
> didn't mention the real data...

Thats okay, during my experiments I'm likely to kill some metadata but
hopefully I can't damage too much data... e2image seems perfect for
that.

									Pavel
-- 
Horseback riding is like software...
...vgf orggre jura vgf serr.