From: a3at.mail@gmail.com
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "open list:EXT4 FILE SYSTEM" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: initialize multi-block allocator before checking block descriptors
Date: Sun, 16 Mar 2014 20:17:13 +0400 [thread overview]
Message-ID: <20140316161637.GA19885@azat> (raw)
In-Reply-To: <CAG5DWog0BDHTh1edtQ+457SmJeL_0MacgZ1gYeNL4sY4yEqZWw@mail.gmail.com>
On Sun, Mar 16, 2014 at 06:10:12PM +0400, Azat Khuzhin wrote:
> On Sun, Mar 16, 2014 at 6:38 AM, <tytso@mit.edu> wrote:
> > 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.
>
> Hi Ted,
>
> I just checked with the last upstream commit d8ec26d7f8287 + patch,
> and xfs tests haven't fallen
> I even update xfstests, still nothing.
>
> /src/xfstests # git describe
> linux-v3.8-336-g3948694
>
> /src/xfstests # ./run_generic.sh
> mke2fs 1.42.8 (20-Jun-2013)
> /dev/sdb1 is mounted; will not make a filesystem here!
> FSTYP -- ext4
> PLATFORM -- Linux/x86_64 debian-virtual-2-6-39 3.13.0+
> MKFS_OPTIONS -- /dev/sdc1
> MOUNT_OPTIONS -- -O bigalloc /dev/sdc1 /xfs-playground/scratch
>
> generic/001 2s ... 2s
> Ran: generic/001
> Passed all 1 tests
>
> # uname -r
> 3.13.0+
>
> Maybe I need more recent kernel?
I've also tested on 3.14.0-rc6+: a4ecdf8 ("Merge branch
'x86-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
And no complaints from xfs-tests, and no errors in dmesg.
Could you give me more information about you playground?
>
> >
> > Cheers,
> >
> > - Ted
>
>
>
> --
> Respectfully
> Azat Khuzhin
--
Respectfully
Azat Khuzhin
next prev parent reply other threads:[~2014-03-16 16:17 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
2014-03-16 14:10 ` Azat Khuzhin
2014-03-16 16:17 ` a3at.mail [this message]
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=20140316161637.GA19885@azat \
--to=a3at.mail@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).