From: Mikhail Morfikov <mmorfikov@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Is it safe to use the bigalloc feature in the case of ext4 filesystem?
Date: Fri, 23 Jul 2021 17:30:13 +0200 [thread overview]
Message-ID: <0dc45cbd-b3b0-97ab-66a9-f68331cb483e@gmail.com> (raw)
In the man ext4(5) we can read the following:
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.kernel.org/index.php/Bigalloc for details.
May clash with delayed allocation (see nodelalloc mount
option).
According to the link above, the info is dated back to 2013,
which is a little bit ancient.
What's the current status of the feature? Is it safe to use
bigalloc on several TiB hard disks where only big files will be
stored?
next reply other threads:[~2021-07-23 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 15:30 Mikhail Morfikov [this message]
2021-07-27 6:24 ` Is it safe to use the bigalloc feature in the case of ext4 filesystem? Andreas Dilger
2021-07-27 23:01 ` Theodore Ts'o
2021-07-28 9:36 ` Mikhail Morfikov
2021-07-29 17:59 ` Theodore Ts'o
2021-07-29 18:32 ` Mikhail Morfikov
2021-07-30 13:57 ` Mikhail Morfikov
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=0dc45cbd-b3b0-97ab-66a9-f68331cb483e@gmail.com \
--to=mmorfikov@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 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).