Re: aarch64 reliability issues

[email protected] (Lloyd Parkes) writes:

>So the "no inodes free" is a misleading error message. No surprise
>there really.

>That message almost certainly means that symlink(2) returned an ENOSPC
>error which has a very long description in the manual page.


It's a kernel message, when the filesystem code cannot allocate an
inode. This of course happens when all inodes are in use, but some
other problem (e.g. if it cannot allocate a buffer) may reach the
same error path and thus print the same message.



>My particular problem seemed to be the ZFS memory pool taking and not
>giving back when it should. I note that you do not seem to be using
>ZFS. I just keep an eye on memory usage using top. I used to have to
>reboot my build boxes when the "Pools" number got up towards 32GB.

ZFS has its own ideas on when to allocate and free memory, which will
also change if or when we get to update the code.