From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Guix System ext4 index full
Date: Wed, 3 Jun 2020 19:06:47 -0400 [thread overview]
Message-ID: <20200603230647.GA18842@jasmine.lan> (raw)
In-Reply-To: <87img7df80.fsf@nckx>
On Wed, Jun 03, 2020 at 11:14:23PM +0200, Tobias Geerinckx-Rice wrote:
> Unfortunately, once that hash table fills up, the premier stable Linux file
> system just… gives up and refuses to write any more data. In a very cryptic
> way.
It's so cryptic... I wonder how often people hit this limit in practice?
Is Guix the only place it happens often? Maybe we can ask the kernel
devs to improve the error reporting here.
next prev parent reply other threads:[~2020-06-03 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 20:21 Guix System ext4 index full Roel Janssen
2020-06-03 20:35 ` Tobias Geerinckx-Rice
2020-06-04 9:33 ` Roel Janssen
2020-06-04 13:05 ` Tobias Geerinckx-Rice
2020-06-04 13:27 ` Tobias Geerinckx-Rice
2020-06-04 18:55 ` Roel Janssen
2020-06-04 19:00 ` Vincent Legoll
2020-06-03 20:43 ` Vincent Legoll
2020-06-03 21:14 ` Tobias Geerinckx-Rice
2020-06-03 23:06 ` Leo Famulari [this message]
2020-06-04 9:27 ` Pierre Neidhardt
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=20200603230647.GA18842@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@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.
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).