linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Daniel Drake <ddrake@brontes3d.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH e2fsprogs] Restore backup superblocks in preen mode
Date: Tue, 8 May 2007 14:14:59 -0400	[thread overview]
Message-ID: <20070508181459.GA31101@thunk.org> (raw)
In-Reply-To: <20070508174324.40EBE7B409F@zog.reactivated.net>

On Tue, May 08, 2007 at 06:43:24PM +0100, Daniel Drake wrote:
> The restoration of backup superblocks seems to be reversed in the current
> e2fsprogs:
> 
> When running without preen mode, e2fsck searches and locates a backup
> superblock and fixes the primary superblock without any user intervention.
> 
> When running in preen mode, e2fsck prints a message describing how the user
> can specify the location of a backup superblock, and exits without doing any
> repair.

That's intentional.  If the priumary superblock is wiped out,
something really bad has happened, and usually the first part of the
filesystem is gone too --- possibly including the first part of the
inode table, which would mean the root inode is gone.  So we do want
the user running e2fsck by hand.

We could argue about whether or not e2fsck should explicitly ask for
permission before using a backup superblock, and possibly printing the
label and validating the size, etc., before using it --- but we
definitely don't want to just blithly use a backup superblock when in
preen mode.

						- Ted

  reply	other threads:[~2007-05-08 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 17:43 [PATCH e2fsprogs] Restore backup superblocks in preen mode Daniel Drake
2007-05-08 18:14 ` Theodore Tso [this message]
2007-05-08 18:52   ` Daniel Drake

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=20070508181459.GA31101@thunk.org \
    --to=tytso@mit.edu \
    --cc=ddrake@brontes3d.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).