Differences between version 4 and revision by previous author of Inode.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Tuesday, September 9, 2003 12:38:40 pm | by CriggieCriggie | Revert |
| Older page: | version 1 | Last edited on Monday, August 18, 2003 6:02:06 am | by AristotlePagaltzis | Revert |
@@ -1,3 +1,6 @@
An [Inode] specifies which [DiskCluster]s a file occupies as well as a few attributes such as creation and last-modification times. To that end it contains a list of direct, indirect, and doubly and triply indirect pointers. On some FileSystems, very small files can be stored directly in the [Inode] itself.
Sophisticated FileSystems create [Inode]s on demand, but with most, the number of [Inode]s on a partition has to be decided on during FileSystem creation. It is rare to run out of [Inode]s unless you have an unusual usage profile such as storing a news spool or [Squid] cache. To see how many [Inode]s are free, use __df -i__.
+
+Check out the section under [ipcop] for a tale of increasing the number of [Inode]s on an [ipcop] box.
+[IsomerMadeMeDoThis]
