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.leg...@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