Hi, "Tanguy Le Carrour" <tan...@bioneland.org> writes:
> Hi Guix, > > For the last 6 years or so, I’ve been happily using Guix Home. > My weekly routine had always been: [...] > $ df -i > Filesystem Inodes IUsed IFree IUse% Mounted on > none 997991 649 997342 1% /dev > /dev/sda1 3276800 3275803 997 100% / > /dev/sda2 11403264 343796 11059468 4% /home > tmpfs 1000329 40 1000289 1% /dev/shm > none 1000329 24 1000305 1% /run/systemd > none 1000329 2 1000327 1% /run/user > none 1000329 1 1000328 1% /var/cache/fontconfig > none 1000329 185 1000144 1% /var/lib/gdm > tmpfs 200065 43 200022 1% /run/user/1000 > ``` > > The inode count is quite low, but the thing is, I haven’t changed much in the > meantime!? And it worked perfectly fine for years!? You are indeed running out of inodes. You do not mention which file system you are using, but given this is a problem, I assume Ext4. > I tried removing a lot of packages from my package list, running with > `--no-grafts`, removing `guix shell` profiles… but nothing helped! > Has anything changed recently in Guix that could have caused this problem? > > Potential solutions that I’m now considering: > > - stop using Guix Home and go back to Stow > - reinstall and stop using a dedicated 50G system partition > > But I have to admit that both are very disappointing to me! > > I would gladly consider any other suggestions! I'd migrate your system to the Btrfs file system, which dynamically allocates inodes and never runs out of them. It has a few peculiarities that must be taken into account, such as the requirement to run 'btrfs balance' periodically to reclaim unallocated blocks, but otherwise it's stable and has interesting features. Make sure to use it with Zstd compression to magically double (about) your storage capacity :-). -- Thanks, Maxim
