All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Robert Gyazig <juliarobertz_fan@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: undo an mke2fs !!
Date: Thu, 6 Nov 2003 12:22:39 -0500	[thread overview]
Message-ID: <20031106172239.GA24360@thunk.org> (raw)
In-Reply-To: <20031106150148.GA27873@atrey.karlin.mff.cuni.cz>

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


  reply	other threads:[~2003-11-06 17:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06  5:56 undo an mke2fs !! Robert Gyazig
2003-11-06 13:34 ` Theodore Ts'o
2003-11-06 14:25   ` Ingo Oeser
2003-11-06 15:01   ` Pavel Machek
2003-11-06 17:22     ` Theodore Ts'o [this message]
2003-11-06 19:21       ` Pavel Machek
2003-11-07 10:33         ` Geert Uytterhoeven
2003-11-07 10:48           ` Pavel Machek
2003-11-07 19:58           ` Theodore Ts'o
2003-11-06 16:54   ` Maciej Zenczykowski
2003-11-07  4:35     ` Szakacsits Szabolcs
2003-11-07  5:00       ` Nathan Scott
2003-11-07  5:43         ` Szakacsits Szabolcs
2003-11-07  5:52           ` Nathan Scott
2003-11-07 23:13       ` Andrew Pimlott
2003-11-08 15:02         ` Szakacsits Szabolcs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031106172239.GA24360@thunk.org \
    --to=tytso@mit.edu \
    --cc=juliarobertz_fan@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.