Talk:Inode

From Wikipedia, the free encyclopedia

"The kaki of a file system that makes use of the concept of inodes surprises many users who are not used to it at first:" What does "kaki" mean? 213.94.245.1 19:50, 27 November 2005 (UTC)

Hehe, obviously vandalism... Reverted. 70.82.141.92 01:08, 4 December 2005 (UTC).....

Contents

[edit] inode stored?

Where is the inode information stored? With the file? Or in a special directory?

Check this out -> Unix_File_System

[edit] mke2fs -i

For anyone who knows enough about it to do so, some discussion here about the balance between having enough inodes available and using up too much space when building a filesystem would be helpful. Examples might include disk space usage and inode count for the same number of files when different -i values are used with mke2fs. --joshua orvis 14:49, 8 January 2007 (UTC)

[edit] Variations in inode file systems

The whole section seems to be a bit schizophrenic. For example:

  1. inode file systems can fragment as severly[sic] as FAT based file systems, yet universally inode file systems lack deframenation tools.
  2. An inode file system would have to be offline to be fully defragmented on most systems -- but some online defragmenation tools exist.

The subsection about i_generation seem to really be either NFS only topics or NFS and Linux only topics.

There's also some odd comparison to FAT32 and NTFS.

I submit that this whole section should be removed. IMHO it has, at best, dubious value. --J3gum (talk) 18:04, 21 February 2008 (UTC)


[edit] Details

The first paragraph here appears to contradict itself: first saying that the number of inodes (and therefore max files) is fixed, but then saying that most file systems can handle unlimited files —Preceding unsigned comment added by 82.11.19.16 (talk) 00:08, 12 March 2008 (UTC)

I agree. I am removing the later phrase, as it is probably the incorrect one. SSPecter Talk|E-Mail ◆ 12:08, 19 March 2008 (UTC).