From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v3 0/6] ext4: rework bigalloc reserved cluster accounting
Date: Tue, 2 Oct 2018 23:15:00 -0400 [thread overview]
Message-ID: <20181003031500.GA30807@thunk.org> (raw)
In-Reply-To: <20180928162316.16480-1-enwlinux@gmail.com>
On Fri, Sep 28, 2018 at 12:23:10PM -0400, Eric Whitney wrote:
> Ext4 can make gross overestimates of the number of reserved clusters
> required to handle bigalloc write requests under delayed allocation,
> resulting in premature ENOSPC and quota limit failures.
>
> These patches fix the implementation of reserved cluster accounting for
> bigalloc file systems configured to use delayed allocation, and fix the
> specific bugs described in bugzilla #151491.
Thanks, I've applied this patch series to the ext4 git tree.
- Ted
prev parent reply other threads:[~2018-10-03 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 16:23 [PATCH v3 0/6] ext4: rework bigalloc reserved cluster accounting Eric Whitney
2018-09-28 16:23 ` [PATCH v3 1/6] ext4: generalize extents status tree search functions Eric Whitney
2018-09-28 16:23 ` [PATCH v3 2/6] ext4: add new pending reservation mechanism Eric Whitney
2018-09-28 16:23 ` [PATCH v3 3/6] ext4: fix reserved cluster accounting at delayed write time Eric Whitney
2018-09-28 16:23 ` [PATCH v3 4/6] ext4: reduce reserved cluster count by number of allocated clusters Eric Whitney
2018-09-28 16:23 ` [PATCH v3 5/6] ext4: adjust reserved cluster count when removing extents Eric Whitney
2018-09-28 16:23 ` [PATCH v3 6/6] ext4: fix reserved cluster accounting at page invalidation time Eric Whitney
2018-10-03 3:15 ` Theodore Y. 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=20181003031500.GA30807@thunk.org \
--to=tytso@mit.edu \
--cc=enwlinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.