| 1 |
Quick googling around indicates that JFS, or XFS don't have these limitation. |
| 2 |
-----quote-------- |
| 3 |
Many computer programs used by system administrators in UNIX operating systems often designate files with inode numbers. Examples include popular disk |
| 4 |
integrity checking utilities such as the fsck or pfiles. Thus, the need naturally arises to translate inode numbers to file pathnames and vice versa. This can |
| 5 |
be accomplished using the file finding utility find with the -inum option, or the ls command with the proper option (-i on POSIX compliant platforms). |
| 6 |
|
| 7 |
It is possible to use up a device's set of inodes. When this happens, new files cannot be created on the device, even though there may be free space |
| 8 |
available. For example, a mail server may have many small files that don't fill up the disk, but use many inodes to point to the numerous files. |
| 9 |
|
| 10 |
Filesystems (such as JFS, or XFS) escape this limitation with extents and/or dynamic inode allocation, which can 'grow' the filesystem and/or increase the |
| 11 |
number of inodes. |
| 12 |
----end quote------ |
| 13 |
|
| 14 |
-- |
| 15 |
Joseph |
Archives