From: "Lukáš Czerner" <lczerner@redhat.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"matthew@wil.cx" <matthew@wil.cx>
Subject: Re: xfstests failures in v3.13-rc7
Date: Wed, 8 Jan 2014 12:53:09 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1401081248030.2257@localhost.localdomain> (raw)
In-Reply-To: <1389063428.2169.12.camel@ancientdefender.lm.intel.com>
On Tue, 7 Jan 2014, Verma, Vishal L wrote:
> Date: Tue, 7 Jan 2014 02:57:13 +0000
> From: "Verma, Vishal L" <vishal.l.verma@intel.com>
> To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
> Cc: "matthew@wil.cx" <matthew@wil.cx>
> Subject: xfstests failures in v3.13-rc7
>
> Hi,
>
> I have been running xfstests with ext4 on a ramdisk (brd), and noticed a
> few tests were failing with an inconsistent file system at the end of
> the test.
>
> The following fail for v3.13-rc7:
> generic/013
> generic/083
> generic/269
> generic/321 (this one is not inconsistent fs, see log)
> generic/322
Hi,
Unfortunately you have not provided *.full logs, but I believe that
at least 013, 083 and 269 failures are caused by bug in e2fsprogs
which was fixed with:
085757fcc22a86168ee6793dfad9a95d88fb09db e2fsck: don't report uninit
extents past EOF invalid
which is present in the lates e2fsprogs release 1.42.9.
Please retest with that.
Thanks!
-Lukas
>
> The output of xfstests for these failures is also attached.
>
> It looks like generic/013 should be resolved by:
> http://thread.gmane.org/gmane.comp.file-systems.ext4/42032
> Are any of the others known failures, especially for brd?
>
> Thanks,
> -Vishal
>
>
prev parent reply other threads:[~2014-01-08 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 2:57 xfstests failures in v3.13-rc7 Verma, Vishal L
2014-01-07 12:01 ` Jan Kara
2014-01-08 4:56 ` jon ernst
2014-01-08 10:33 ` Matthew Wilcox
2014-01-09 2:09 ` Verma, Vishal L
2014-01-11 21:58 ` Theodore Ts'o
2014-01-14 4:02 ` Verma, Vishal L
2014-01-08 11:53 ` Lukáš Czerner [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=alpine.LFD.2.00.1401081248030.2257@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox