linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: fdbugs <fdbugs@dupoux.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: bug when we do an mkfs.ext4 + tune2fs
Date: Tue, 20 Jan 2009 09:05:10 -0500	[thread overview]
Message-ID: <20090120140510.GC10037@mit.edu> (raw)
In-Reply-To: <580e35610901200521x20a9bc85l66ea520151008bc9@mail.gmail.com>

On Tue, Jan 20, 2009 at 01:21:45PM +0000, fdbugs wrote:
> Hi,
> 
> I have an error when I try to mount an ext4 after having changed its
> uuid with tune2fs. If I just do an mkfs.ext4 I can mount it, but if I
> do an mkfs.ext4 and then an e2label -U on it, it can't be mounted.
> Fortunately this bug is quite easy to reproduce.

This is a bug in tune2fs/e2label; it's fixed in the maint branch of
e2fsprogs, and I hope to get a release out soon.  The relevant commit
is:

commit 9d4a4dc2870c46c74f815ec2bebe10b4701accf2
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Fri Nov 14 17:42:27 2008 -0500

    tune2fs: Update the block group checksums when changing the UUID
    
    Since the block group checksums depend on the UUID, we need to update
    the block group checksums when setting the UUID.  We only do so if all
    of the checksums are correct, however.
    
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

You can work around it by using the command "e2fsck -fy" right after
the e2label -U, but that's admittedly quite annoying.  :-/

							- Ted

      reply	other threads:[~2009-01-20 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 13:21 bug when we do an mkfs.ext4 + tune2fs fdbugs
2009-01-20 14:05 ` Theodore Tso [this message]

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=20090120140510.GC10037@mit.edu \
    --to=tytso@mit.edu \
    --cc=fdbugs@dupoux.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).