I want to see how many files are in subdirectories to find out where all the inode usage is on the system. Kind of like I would do this for space usage
So I received a warning from our monitoring system on one of our boxes that the number of free inodes on a filesystem was getting low.
I find that under my root directory, there are some directories that have the same inode number:
Let’s say when I do
ls -li inside a directory, I get this:
It is well-known that empty text files have zero bytes:
Say I am running a software, and then I run package manager to upgrade the software, I notice that Linux does not bring down the running process for package upgrade – it is still running fine. How does Linux do this?
I changed the /home directory to a different partition and couldn’t access the files from it, something I have been able to solve from this question – How do you access the contents of a previous mount after switching to a different the partition?.
I understand the size reported by ls corresponds with number of inodes inside the directory, not their actual size. I have noticed peculiar behavior, when…
My root filesystem is running out of inodes. If this were an issue of disk space, I’d use
du -s to get a top-level overview of where the space is going, then head down the directory tree to find particular offenders. Is there an equivalent option for inodes?
I have several files with encoding issues in their file names (German umlauts, burned on CD with Windows, read by Windows and synced to Linux with Seafile. Something, somewhere went wrong…).
Bash and zsh only show “?” instead of umlauts,
stat shows something like