From: ludo@gnu.org (Ludovic Courtès)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: No more space left on device issue
Date: Wed, 21 Dec 2016 22:48:34 +0100 [thread overview]
Message-ID: <87a8bpuf65.fsf@gnu.org> (raw)
In-Reply-To: <874m1xazcm.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 21 Dec 2016 10:52:57 -0800")
Hello Maxim!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Indeed, it’s low on free inodes. :-)
>>
>> That said, 37 G is not that much (my laptop’s root partition, which
>> includes the store, is 64 G, and I expect most users are in this
>> ballpark).
>
> I understand that my partition size is not very large; This is a 2011
> era laptop with a 64 GB SSD. Although quite dated and behind todays'
> standard, it's useful in exposing the limits of the software faster ;).
Right; what I meant is that 37 G shouldn’t cause any problems because
it’s relatively small.
> What I don't understand is why the all the inodes are used at only 71%
> of disk usage (11GB left!). There's not much else than Guix there; I
> have a documents folder (700 MB with 4k files) and some git
> repositories (2.6 GB, 38k files), but that's it.
Not sure, I don’t know of inode usage profiling tools.
Does running “guix gc” help?
> Assuming that the problem is related to the Guix store being very
> file/link intensive and that the Hydra servers deplete their inodes at a
> similar ratio, that would lead to their 1.5 TB EXT4 filesystem being
> more like 1 TB of usable storage.
[...]
> I guess we can't really compare ext3 and ext4. We'd need a filesystem
> versed person to shed some light here. I'd be more interested to know if
> the Hydra servers can (nearly) max their ext4 filesystem without running
> out of inodes.
FWIW, on hydra.gnu.org we have this:
--8<---------------cut here---------------start------------->8---
$ df -i /gnu/store
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda1 98304000 6864127 91439873 7% /
$ df -h /gnu/store
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 1.5T 521G 881G 38% /
--8<---------------cut here---------------end--------------->8---
On mirror.hydra.gnu.org:
--8<---------------cut here---------------start------------->8---
$ df -i /gnu/store
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/vg0-store 100663296 10988332 89674964 11% /gnu
$ df -h /gnu/store
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-store 1.5T 1.4T 103G 93% /gnu
--8<---------------cut here---------------end--------------->8---
Ludo’.
next prev parent reply other threads:[~2016-12-21 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 19:16 No more space left on device issue Maxim Cournoyer
2016-12-19 13:52 ` Ludovic Courtès
2016-12-21 18:52 ` Maxim Cournoyer
2016-12-21 21:48 ` Ludovic Courtès [this message]
2016-12-21 22:17 ` Tobias Geerinckx-Rice
2016-12-22 18:00 ` Maxim Cournoyer
2016-12-22 17:41 ` Maxim Cournoyer
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=87a8bpuf65.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@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.
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).