From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ENOSPC inline_data fsck failure
Date: Sat, 29 Feb 2020 13:17:11 -0500 [thread overview]
Message-ID: <20200229181711.GD7378@mit.edu> (raw)
In-Reply-To: <20200228105234.n5wt5x2vi3ftxuyh@xzhoux.usersys.redhat.com>
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
next prev parent reply other threads:[~2020-02-29 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:52 ENOSPC inline_data fsck failure Murphy Zhou
2020-02-29 18:17 ` Theodore Y. Ts'o [this message]
2020-03-02 7:04 ` Murphy Zhou
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=20200229181711.GD7378@mit.edu \
--to=tytso@mit.edu \
--cc=jencce.kernel@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).