From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 46905@debbugs.gnu.org
Subject: bug#46905: Add a note about ext4's dir_index to the manual
Date: Thu, 04 Mar 2021 23:01:26 +0100 [thread overview]
Message-ID: <87blbymvd5.fsf@gnu.org> (raw)
In-Reply-To: <87v9a89c8v.fsf@nckx> (Tobias Geerinckx-Rice's message of "Wed, 03 Mar 2021 22:08:16 +0100")
Hi!
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Mainly a reminder to myself to do so.
>
> Guix can break ext4, and more than once has, with a inscrutable error
> message. We should document it explicitly.
>
> See <http://logs.guix.gnu.org/guix/2021-03-03.log#220037>.
You wrote:
--8<---------------cut here---------------start------------->8---
<nckx>OK, that's the culprit (it's common: ext4 has a design flaw in that it hashes directory entries and... just
dies when the hash table gets ‘full’). Try ‘tune2fs -E "hash_alg=tea" /dev/foo’ to select a different hash algo, or
‘tune2fs -O "^dir_index" /dev/foo’ to disable it completely if that doesn't help.
--8<---------------cut here---------------end--------------->8---
Really? I’ve almost always used ‘dir_index’ in my Guix + NixOS days,
and IIRC store accesses were much slower before that was a thing.
On berlin, /gnu is a 37 TiB file system with ‘dir_index’ turned on and
it works well.
I don’t think we can claim there’s a design flaw. WDYT?
Ludo’.
next prev parent reply other threads:[~2021-03-04 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:08 bug#46905: Add a note about ext4's dir_index to the manual Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-04 22:01 ` Ludovic Courtès [this message]
2021-03-04 22:38 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-08 14:26 ` Ludovic Courtès
2021-03-04 22:28 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blbymvd5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=46905@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).