unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jaft via <help-guix@gnu.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>,
	phodina <phodina@protonmail.com>
Subject: Re: Running Out of Inodes
Date: Tue, 16 Nov 2021 08:11:41 +0000 (UTC)	[thread overview]
Message-ID: <1207051399.2184779.1637050301121@mail.yahoo.com> (raw)
In-Reply-To: <CAEwRq=rRJ1coaLH3vXnEWfyzbZoCUQS_oRgG8iwdnbHWRXejoA@mail.gmail.com>

 Mmm; that makes sense. 'Dunno why my brain interpreted it as "more inodes"; thanks for pointing it out.
I just opted to make /gnu/store its own Btrfs partition; I don't trust myself to be able to properly estimate how many inodes I might need and it's been working really well, thus far.
Thanks for the info. you provided, though; it was helpful in understanding what's going on.
Jonathan
    On Sunday, November 14, 2021, 03:01:39 PM CST, Vincent Legoll <vincent.legoll@gmail.com> wrote:  
 
 Hello,

On Sun, Nov 14, 2021 at 7:58 PM Jaft via <help-guix@gnu.org> wrote:
> Heh, – well – I tried the large_dir suggestion in that thread and GRUB had
> the same freak-out (in retrospect, not surprising as the E-mails are only from
> 2020; dunno why I thought I'd seen 2017, on first read…).

There's a "2017" mention in the thread referenced by Petr, maybe that's where
you saw it.

> using a root partition of about 46G
> 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.

If your problem is really being out of free inodes, I don't think the
"large_dir"
option is your solution, because it only increase the number of files per
directory limit, it does not increase the available number of inodes.

Maybe you should manually create the filesystem with mke2fs and specify
a bigger number of inodes with its "-N" parameter.

Tell us if you find a way around the problem.

-- 
Vincent Legoll
  

  parent reply	other threads:[~2021-11-16  8:13 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 ` Running Out of Inodes Jaft via
2021-11-14 13:47   ` 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 [this message]
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=1207051399.2184779.1637050301121@mail.yahoo.com \
    --to=help-guix@gnu.org \
    --cc=phodina@protonmail.com \
    --cc=vincent.legoll@gmail.com \
    --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).