unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jaft via <help-guix@gnu.org>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Running Out of Inodes
Date: Sun, 14 Nov 2021 11:14:40 +0000 (UTC)	[thread overview]
Message-ID: <833262586.1528194.1636888480202@mail.yahoo.com> (raw)
In-Reply-To: 833262586.1528194.1636888480202.ref@mail.yahoo.com

Hey, hey.
It could very well be my own ignorance about things but I'm running into an issue that I wouldn't think I'd run into so naïvely; if there's any further light to be shed, I very much appreciate it.
I wanted to try out Guix so I installed it to a laptop I have; the previous distro I had on there had been using a root partition of about 46G so I just decided to keep the same partition setup (though reformatting each one).
About 17 packages in, I started getting a "No space left on device" error; looking closer at it, – while I still had ~20% of free disk space available – I was fresh out of free inodes. I remembered that someone I'd read, somewhere, had said you'd probably want, at least, 50G for Guix so I figured I probably shot myself in the foot with so small a root and just opted to reinstall.
This time, I deleted the home partition and the root one to create one 156G partition for the entire install and figured that'd be sufficient (I've been using ext4 for these, in case that information is relevant, any).
This time, though, I managed 21 packages before running into the same issue.
There's still 70% of the disk space free but I'm entirely out of free inodes; leastwise, I was but I tried a guix gc, just to see what all got freed up, and, now, I have 5% of all inodes free.
Is this relatively typical? I figured I hadn't done anything particularly out of ordinary usage (Guix's new to me so I literally just did an install and then started installing packages from the gnu channel).
Let me know if there's any further or more particular info. to include, if that'd help; I just wouldn't know what to provide.
Thanks!
Jonathan

       reply	other threads:[~2021-11-14 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <833262586.1528194.1636888480202.ref@mail.yahoo.com>
2021-11-14 11:14 ` Jaft via [this message]
2021-11-14 13:47   ` Running Out of Inodes phodina via
2021-11-14 18:47     ` Jaft via
2021-11-14 21:01       ` Vincent Legoll
2021-11-15  6:46         ` Dr. Arne Babenhauserheide
2021-11-16  8:11         ` Jaft via
2021-11-15  3:18       ` Thiago Jung Bauermann
2021-11-16  8:14         ` Jaft via
2021-11-19 19:09           ` Paul Jewell

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=833262586.1528194.1636888480202@mail.yahoo.com \
    --to=help-guix@gnu.org \
    --cc=wamm_kd_schmelingski@yahoo.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).