[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1401081248030.2257@localhost.localdomain>
Date: Wed, 8 Jan 2014 12:53:09 +0100 (CET)
From: Lukáš Czerner <lczerner@...hat.com>
To: "Verma, Vishal L" <vishal.l.verma@...el.com>
cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"matthew@....cx" <matthew@....cx>
Subject: Re: xfstests failures in v3.13-rc7
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@...el.com>
> To: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
> Cc: "matthew@....cx" <matthew@....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
>
>
--
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