unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: Roel Janssen <roel@gnu.org>, help-guix@gnu.org
Subject: Re: Guix System ext4 index full
Date: Wed, 03 Jun 2020 23:14:23 +0200	[thread overview]
Message-ID: <87img7df80.fsf@nckx> (raw)
In-Reply-To: <903fccce-48f4-047c-0b7e-90bbeb8a597d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Vincent Legoll 写道:
> I think the filesystem (or directory) is full of inodes.

No, but it's a similar hard limit, and one that not even ‘df -i’ 
will warn you about.

Ext4's dir_index feature uses hash tables to look up directory 
entries, so that for directories with a very large number of items 
(like /gnu/store!), the kernel doesn't have to do the horribly 
slow equivalent of:

  for i in *; do …; done

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.

The large_dir flag ‘increases the limit’ (the man page does not 
say by how much) but it doesn't go away.

Your hash table is full of eels,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-06-03 21:14 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 [this message]
2020-06-03 23:06     ` Leo Famulari
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=87img7df80.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=roel@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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).