From: "Theodore Ts'o" <tytso@mit.edu>
To: "Kiselev, Oleg" <okiselev@amazon.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Does `-O bigalloc` still conflict with `delalloc`?
Date: Fri, 27 May 2022 22:31:07 -0400 [thread overview]
Message-ID: <YpGJa/f3dSh2XZwb@mit.edu> (raw)
In-Reply-To: <923065C9-2EFB-4F59-895E-139B4B9F9E98@amazon.com>
On Sat, May 21, 2022 at 02:39:00AM +0000, Kiselev, Oleg wrote:
> The `ext4(5)` man page, contained in the most recent e2fsprogs still says:
>
> Warning: The bigalloc feature is still under development, and may not be fully supported
> with your kernel or may have various bugs. Please see the web page http://ext4.wiki.ker‐
> nel.org/index.php/Bigalloc for details. May clash with delayed allocation (see nodelal‐
> loc mount option).
>
> Is a bad interaction with `delalloc` still an issue and should we be using the `nodelalloc` option?
Apologies for not getting back to you right away. I wanted to check
with some folks on the ext4 team, and in fact we talked about it at
this week's ext4 video chat. Eric Whitney worked on fixing bigalloc
and delalloc, and it looks like the last of the fixes landed in Linux
version 5.4 in 2019. So that warning in the ext4(5) man page is
definitely out of date.
I'll remove it in the next release of e2fsprogs.
Cheers,
- Ted
next prev parent reply other threads:[~2022-05-28 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 2:39 Does `-O bigalloc` still conflict with `delalloc`? Kiselev, Oleg
2022-05-28 2:31 ` Theodore Ts'o [this message]
2022-05-28 8:30 ` Kiselev, Oleg
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=YpGJa/f3dSh2XZwb@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=okiselev@amazon.com \
/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