From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Lukas Czerner <lczerner@redhat.com>
Subject: Re: [PATCH] ext4: Do not reserve clusters when fs doesn't support extents
Date: Sun, 8 Dec 2013 21:13:59 -0500 [thread overview]
Message-ID: <20131209021359.GA27144@thunk.org> (raw)
In-Reply-To: <1385638965-14674-1-git-send-email-jack@suse.cz>
On Thu, Nov 28, 2013 at 12:42:45PM +0100, Jan Kara wrote:
> When filesystem doesn't support extents (like in ext2/3 compatibility
> modes), there is no need to reserve any clusters. Space estimates for
> writing are exact, hole punching doesn't need new metadata, and there
> are no unwritten extents to convert.
>
> This fixes a problem when filesystem still having some free space when
> accessed with a native ext2/3 driver suddently reports ENOSPC when
> accessed with ext4 driver.
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> CC: Lukas Czerner <lczerner@redhat.com>
> Signed-off-by: Jan Kara <jack@suse.cz>
Thanks, applied. Given that distro's are using
CONFIG_EXT4_USE_FOR_EXT23, I'm going to queue this for the stable kernel.
- Ted
prev parent reply other threads:[~2013-12-09 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 11:42 [PATCH] ext4: Do not reserve clusters when fs doesn't support extents Jan Kara
2013-11-28 12:47 ` Geert Uytterhoeven
2013-11-29 12:01 ` Lukáš Czerner
2013-12-09 2:13 ` 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=20131209021359.GA27144@thunk.org \
--to=tytso@mit.edu \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=lczerner@redhat.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).