[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1304945752.11788.11.camel@heisenberg.scientia.net>
Date: Mon, 09 May 2011 14:55:52 +0200
From: Christoph Anton Mitterer <calestyo@...entia.net>
To: linux-ext4@...r.kernel.org
Subject: Re: errors in ext4_mb_generate_buddy and ext4_remount
Hi Ted.
On Sun, 2011-05-08 at 21:01 -0400, Ted Ts'o wrote:
> Kernels 2.6.35 and newer will set superblock fields that will result
> in those messages. They're not error messages per se; it's just a
> notification that there was an file system error in the past that
> hasn't been fixed yet. In your case, it *has* been fixed, but you
> don't have a new enough version of e2fsprogs so that it clears the
> relevant parts of the superblock.
Thanks for that explanation.
> The debian packages of e2fsprogs version 1.41.14-1 in experimental, or
> 1.41.12-4 in unstable
Ah, I haven't tried it with the one that was uploaded to unstable
yet.... will give it a try later.
Another thing. Perhaps you've seen my post where I've unfortunately
overridden an (important ;) ) ext3 fs with mkfs, instead of doing fsck.
Of course this is my fault but do you see any chance to add checks to
mke2fs whether any known fs/partition type/other containter like
luks/mdadm/etc. is on the device? (And of course require a
--force=I-really-know-what-I-do™ parameter to the evil.)
Cheers,
Chris.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists