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?
Is it possible to mount a loopback file as read-only, and redirect all writes to RAM?
I am reading this intro to the command line by Mark Bates.
After mount there are listed some filesystems. I need to know what’s in the /dev, /proc and /sys. Some examples would be great!
I am new to Linux so pardon me for the possible confusion you may encounter in this question.
May you have ever used filesystem defragmentation tools (like Norton SpeedDisk or Piriform Defraggler) on Windows, you have probably seen such a diagram:
The distribution is an Ubuntu server running the 2.6.35-30 Linux kernel.
I need to do a destructive (rw) test on a new drive, and a read-only on a drive that fell out of my RAID array. I want to see if it finds problems and how far along it is.
While answering this U&L question titled: What command do I use to see the start and end block of a file in the file system?, I tried to figure out if it was possible to determine a file’s LBA using it’s inode.
In the context of operating system control tables, does the term “file tables” refer to a data structure that is part of the filesystem, or that is in main memory (and in which case I assume it would only have references to open files)? My textbook1 says,