> can someone explain what a inode is and > how that is related to filesytem, blocksize, harddrive. inodes aren't used with every filesystem. MSDOS, for instance, uses "allocation units" for header info and data. I forget what the "i" in inode stands for but I've always known it to be "index." inodes are places on the filesystem where file header information is kept. There is one inode per file. The inode contains information about file creation, access, modification, and deletion times (in UNIX time format).. it contains information about the link count (for directories, the link count is 2 plus one for every subdirectory.. and for files, the link count is 1 plus 1 for every hard link the file has).. it contains file type, mode, attribute, and owner/group information. It also contains a list of the blocks that are allocated to hold the data of the file. Think of inodes as checks, and the blocks as your funds: You can run out of blocks but still have inodes available... similarly, you can run out of inodes before you run out of blocks. Check your inode availability with "df -i". Check block availability with "df". Check disk usage info in human readable format with "df -h". In most cases you'll have many more inodes free than blocks free, unless you have thousands of <1KB files or there abouts, which can happen. Drive maintenance (manual searching and erasing unused stuff is always a good idea). This is what my system currently has: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hda7 2064384 80326 1984058 4% / /dev/hda1 2000 23 1977 1% /boot /dev/hda5 1048576 10016 1038560 1% /home Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda7 7964049 2380052 5171129 32% / /dev/hda1 7746 2201 5145 30% /boot /dev/hda5 4052132 2106624 1735862 55% /home Note how I'm using a lot more blocks than inodes. On /dev/hda1, I have 2000 inodes which I can use total on that filesystem. I have 23 of them in use, which means I have 23 files, directories, and anything else that uses inodes up. On that same filesystem, I have 7746 blocks total. 1 block = 1KB on Second Extended (ext2). How big is an inode? I don't remember offhand. Note: On a filesystem check, you might get a warning about an inode having a zero dtime... this means that an inode was marked deleted (perhaps with a link count of 0) but was never given a non-zero value for its dtime (deleted time) field. Um.. read man pages, etc. You'll learn it all over time :) I'm sure others who reply to this email will be able to offer some more info. -Statux _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
