Path: utzoo!utgpu!watmath!clyde!att!osu-cis!killer!texbell!uhnix1!nuchat!steve
From: steve@nuchat.UUCP (Steve Nuchia)
Newsgroups: comp.unix.microport
Subject: Re: How does Microport System V/AT handle bad blocks?
Message-ID: <2788@nuchat.UUCP>
Date: 3 Jan 89 14:00:16 GMT
References: <460@tarpit.UUCP> <326@focsys.UUCP> <464@tarpit.UUCP> <2689@nuchat.UUCP> <211@trevan.UUCP> <798@splut.UUCP>
Reply-To: steve@nuchat.UUCP (Steve Nuchia)
Organization: Houston Public Access
Lines: 24


In article <798@splut.UUCP> Jay Maynard writes:
>In article <211@trevan.UUCP> trevor@trevan.UUCP (trevor) writes:
>>Well well I spent a whole week trying to sort my disks out and now it
>>turns out to be FSCK to be at fault. Microport does admit to there being
>>a problem but it says only with file systems greater tan 130000 blocks.
>>All my file systems are less than 100,000 blocks and I still get this
>>problem.

>I first encountered this problem on an 84K block filesystem. I spent a
>week with fsdb and fsck, using fsdb to straighten out the worst

With the default number of inodes the problem is rare or nonexistent
under 130000 blocks.  Mkfs will give you something like 13000 inodes
in that case, which is a little light for storing a full news feed.
If you run a 120000 block filesystem with say 20000 inodes it will
definitely trigger the bug, at least when sufficiently full.


[filler line, sorry.]
-- 
Steve Nuchia	      South Coast Computing Services
uunet!nuchat!steve    POB 890952  Houston, Texas  77289
(713) 964 2462	      Consultation & Systems, Support for PD Software.