det@hawkmoon.MN.ORG (Derek E. Terveer) (07/02/88)
I suppose that this subject has erupted before but, obviously, i don't have the information that was revealed in that thrashing... (sigh...) In B2.11.14 News a "problem" that i have noticed that affects the running of my systems directly is that News seems to demand that /usr/spool/news, if mounted on a seperate file system, not have any seperate file systems mounted as sub- directories. Permit me an example: / (/dev/dsk/0s1 ): 8314 blocks 1900 i-nodes /usr (/dev/dsk/0s3 ): 2658 blocks 3622 i-nodes /usr/spool/news (/dev/dsk/1s3 ): 11336 blocks 10840 i-nodes /usr/spool/news/comp (/dev/dsk/0s4 ): 14090 blocks 8781 i-nodes /mnt/tmp (/dev/dsk/f0q15dt): 1056 blocks 157 i-nodes I had, until i ran into the problem, /dev/dsk0s4 mounted on /usr/spool/news/comp to increase my total /usr/spool/news space. I put it on comp, 'cause that is by far my biggest distribution. However, after about 2 days of running in this configuration the /usr/spool/news fs was trashed. I had to run fsck on it a couple of times to restore it to sanity. Apparently (just guessing here w/o consulting the sources), News forges links beween files without checking that its on a seperate fs and somehow this is screwing up the overall fs tree (understandably). Now, the problem is that from the above it appears that the News spool area is limited to a single fs. This is all very nice, but a number of my systems have enough space to handle the news feeds i'm getting, but not all on one disk! I have, for example, on one system two 40M drives with one of the 40Meggers mounted as /usr/spool/news. Now i can sacrifice about 20M out of / (since / doesn't really need an extra 20M (:-)), but i can't mount it as a sub directory of /usr/spool/news. Any ideas on how to configure News to get around this feature, or am i just stuck? Or have i overlooked something real obvious?? derek -- Derek Terveer det@hawkmoon.MN.ORG uunet!rosevax!elric!hawkmoon!det