[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.23) What do these history.n.* files do?
Next Document: (7.25) Server throttled No space left on device writing article file
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.23) What do these history.n.* files do?
Next Document: (7.25) Server throttled No space left on device writing article file
(7.24) Out of inodes but still space left on disk
If you have still space on your disk but no more inodes then you should consider rebuilding the partition on which your spool is. Default options for filesystems are mostly to use 4k / inode. For a newsfs this isn't appropriate, as articles are in average under 3k. So create your newsspool with 2k per inode. If you rebuild you also could adjust the values for block-/fragsize to 4096/512 so you'll get more space out of your disk than on 8192/1024 (this will be a bit slower than 8k/1k for articles bigger than 4k, which are a minority so don't use it on a partition dedicated to alt.binaries)
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.23) What do these history.n.* files do?
Next Document: (7.25) Server throttled No space left on device writing article file
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update November 22 2008 @ 00:13 AM