[TriLUG] Reclaiming inodes
Peter Neilson via TriLUG
trilug at trilug.org
Thu Sep 28 09:58:50 EDT 2017
Sure looks like the fs somehow wasn't provisioned with enough inodes when
it was created. My Ubuntu Trusty system has 58M of them, of which I'm
using 2.4M. Make a better fs and copy to it, I guess.
On Thu, 28 Sep 2017 09:48:32 -0400, Thomas Delrue via TriLUG
<trilug at trilug.org> wrote:
> I'm in a bit of a bind and have never seen this before so if anyone can
> explain to me what is happening, that would be great:
>
> I have a machine that keeps reporting that it's run out of disk space.
> So I do the usual "df -h" and get this:
> username at host ~ $ df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/root 12G 3.9G 7.1G 36% /
> devtmpfs 997M 0 997M 0% /dev
> tmpfs 999M 0 999M 0% /dev/shm
> tmpfs 999M 9.5M 990M 1% /run
> tmpfs 5.0M 0 5.0M 0% /run/lock
> tmpfs 999M 0 999M 0% /sys/fs/cgroup
>
> But it reports that it has no more disk space, so I dig a little deeper
> and I
> find that I could also run df with the -i (inodes) flag, which gives me
> this:
>
> username at host ~ $ df -hi
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/root 735K 735K 0 100% /
> devtmpfs 250K 1.4K 248K 1% /dev
> tmpfs 250K 1 250K 1% /dev/shm
> tmpfs 250K 1.2K 249K 1% /run
> tmpfs 250K 3 250K 1% /run/lock
> tmpfs 250K 16 250K 1% /sys/fs/cgroup
>
> I appear to have "run out of inodes"? Is there a way to reclaim them?
>
> Thanks
> Thomas
More information about the TriLUG
mailing list