Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 27 May 2022 22:31:07 -0400
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`?
Message-ID: <YpGJa/f3dSh2XZwb@mit.edu>
References: <923065C9-2EFB-4F59-895E-139B4B9F9E98@amazon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <923065C9-2EFB-4F59-895E-139B4B9F9E98@amazon.com>
Precedence: bulk

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