From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Phillip Susi <psusi@ubuntu.com>, linux-ext4@vger.kernel.org
Subject: Re: e2fsck and backup superblocks
Date: Sat, 18 Feb 2012 17:31:31 -0500 [thread overview]
Message-ID: <20120218223131.GB8320@thunk.org> (raw)
In-Reply-To: <4F3F1580.9020108@redhat.com>
On Fri, Feb 17, 2012 at 07:05:36PM -0800, Eric Sandeen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2/17/12 7:00 PM, Phillip Susi wrote:
> > I have noticed that e2fsck always complains about block group descriptor checksums being invalid when run on a backup superblock, even when run again immediately after being told to fix them. Is there some odd intentional behavior here I'm not aware of?
>
> Check the list for:
>
> "[PATCH] libext2fs: quiet spurious group checksum errors"
Which is in e2fsprogs 1.42.1....
- Ted
next prev parent reply other threads:[~2012-02-18 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 3:00 e2fsck and backup superblocks Phillip Susi
2012-02-18 3:05 ` Eric Sandeen
2012-02-18 22:31 ` Ted Ts'o [this message]
2012-02-20 3:11 ` Eric Sandeen
2012-02-20 3:19 ` E2fsprogs 1.42.1 release Ted Ts'o
2012-02-20 18:59 ` Eric Sandeen
2012-02-20 19:01 ` Eric Sandeen
2012-02-20 19:18 ` Ted Ts'o
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=20120218223131.GB8320@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=psusi@ubuntu.com \
--cc=sandeen@redhat.com \
/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.