[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200302070417.ldaoyxenqkixny43@xzhoux.usersys.redhat.com>
Date: Mon, 2 Mar 2020 15:04:17 +0800
From: Murphy Zhou <jencce.kernel@...il.com>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: Murphy Zhou <jencce.kernel@...il.com>, linux-ext4@...r.kernel.org
Subject: Re: ENOSPC inline_data fsck failure
On Sat, Feb 29, 2020 at 01:17:11PM -0500, Theodore Y. Ts'o wrote:
> On Fri, Feb 28, 2020 at 06:52:34PM +0800, Murphy Zhou wrote:
> >
> > With inline_data mkfs option, generic/083 can easily trigger
> > a fsck failure like this:
> >
> > The testcase is doing a simple testing: make a small(256M) fs,
> > run fsstress in it, make it out of space. Then fsck.
> >
> > Not sure about is this an issue of ext4 filesystem or e2fsck
> > needs more options.
>
> This is an ext4 bug. It's been on my radar screen to investigate one
> of these days, but I've just never gotten around to it. I'm guessing
> the bug is the error handling case when an inline directory is getting
> converted directory where its contents are stored in data blocks, and
> the block allocation fails due to the ENOSPC.
>
> - Ted
Thanks Ted for the confirmation!
--
Murphy
Powered by blists - more mailing lists