From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: don't retry file block mapping on bigalloc fs with non-extent file
Date: Sun, 21 Jun 2015 21:20:50 -0400 [thread overview]
Message-ID: <20150622012050.GQ29480@thunk.org> (raw)
In-Reply-To: <20150319212557.GG11031@birch.djwong.org>
On Thu, Mar 19, 2015 at 02:25:57PM -0700, Darrick J. Wong wrote:
> ext4 isn't willing to map clusters to a non-extent file. Don't signal
> this with an out of space error, since the FS will retry the
> allocation (which didn't fail) forever. Instead, return EUCLEAN so
> that the operation will fail immediately all the way back to userspace.
>
> (The fix is either to run e2fsck -E bmap2extent, or to chattr +e the file.)
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Applied, thanks.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
prev parent reply other threads:[~2015-06-22 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 21:25 [PATCH] ext4: don't retry file block mapping on bigalloc fs with non-extent file Darrick J. Wong
2015-06-22 1:20 ` Theodore Ts'o [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=20150622012050.GQ29480@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.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).