From: tytso@mit.edu
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: "open list:EXT4 FILE SYSTEM" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: initialize multi-block allocator before checking block descriptors
Date: Sat, 15 Mar 2014 22:38:41 -0400 [thread overview]
Message-ID: <20140316023841.GA902@thunk.org> (raw)
In-Reply-To: <CAG5DWoj0pYD8O17qw_-MK+JX_hsFj04ReUPztShmKWzz45gRbQ@mail.gmail.com>
On Sun, Mar 16, 2014 at 03:54:34AM +0400, Azat Khuzhin wrote:
>
> Thanks Ted, I'll take a look.
> Are you talking about xfs-tests failures?
Yes, the kernel is complaining that the file system looks corrupt.
The xfstest generic/001 is the easist one to trigger it:
generic/001 18s ... [17:35:49][ 26.793766] EXT4-fs error (device vde): ext4_mb_generate_buddy:756: group 1, 32763 clusters in bitmap, 32764
in gd; block bitmap corrupt.
[17:36:09] 20s
[ 39.636943] EXT4-fs (vde): warning: mounting fs with errors, running e2fsck is recommended
I this was using a freshly generated file system using a 20 GiB test
partition, formatted using:
mke2fs -t ext4 -O bigalloc /dev/vde
Dropping the patch made the error go away.
Cheers,
- Ted
next prev parent reply other threads:[~2014-03-16 2:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 21:40 [PATCH] ext4: initialize multi-block allocator before checking block descriptors tytso
2014-03-15 23:54 ` Azat Khuzhin
2014-03-16 2:38 ` tytso [this message]
2014-03-16 14:10 ` Azat Khuzhin
2014-03-16 16:17 ` a3at.mail
2014-03-16 18:46 ` tytso
2014-03-16 20:56 ` a3at.mail
2014-03-17 2:00 ` tytso
2014-03-17 16:19 ` Azat Khuzhin
2014-03-17 17:53 ` a3at.mail
2014-03-25 0:17 ` tytso
2014-03-25 6:24 ` a3at.mail
2014-04-05 15:51 ` Azat Khuzhin
2014-03-17 17:23 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2014-02-10 10:25 Azat Khuzhin
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=20140316023841.GA902@thunk.org \
--to=tytso@mit.edu \
--cc=a3at.mail@gmail.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).