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: Mon, 08 Mar 2021 15:26:46 +0100 [thread overview]
Message-ID: <87r1kpbu1l.fsf@gnu.org> (raw)
In-Reply-To: <87v9a6zgs1.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 04 Mar 2021 23:38:06 +0100")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> I should note that later in the IRC convo I corrected my sloppy ‘full’
> to ‘hash collision’. Unfortunately it just returns an already
> overloaded -ENOSPC to user space.
OK, but when do we get ENOSPC, then?
> Ludovic Courtès 写道:
[...]
>> I don’t think we can claim there’s a design flaw. WDYT?
>
> Fine; implementation flaw, then? Problem is, it's not like there are
> other implementations than the one we're stuck with, so it matters
> little what we call it.
My point is that we shouldn’t suggest that ext4 + dir_index is flawed
or unsuitable for Guix use, because we have strong evidence suggesting
otherwise. :-)
Now, I agree that if there are bugs or limitations hit in some
situations, we should document (or fix) them.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-03-08 14:27 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
2021-03-04 22:38 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-08 14:26 ` Ludovic Courtès [this message]
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=87r1kpbu1l.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).