home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.xenix.sco
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!gumby!yale!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!convex!egsner!adaptex!adaptx1!neese
- From: neese@adaptx1.UUCP (Roy Neese)
- Subject: Re: OUT OF INODES - fsck/filesystem trouble
- Organization: Adaptec Inc., Texas
- Date: Wed, 09 Dec 1992 20:02:42 GMT
- Message-ID: <1992Dec09.200242.8189@adaptx1.UUCP>
- References: <1992Nov30.230842.810@oneb.almanac.bc.ca>
- Lines: 31
-
- In article <1992Nov30.230842.810@oneb.almanac.bc.ca> kmcvay@oneb.almanac.bc.ca (Ken Mcvay) writes:
- > System: SCO XENIX 2.3.2 GT
- >
- > I have a recurring problem which cannot be eliminated without re-installing
- > the o/s, which I am loath to do, since I'd have to back up 110 megs to
- > floppies :-(
- >
- > There are two bad sectors on the SCSI disk which I cannot add to the (empty)
- > badtrk table, either because I didn't leave room for it at installation, or
- > because the SCSI support is broken with 2.3.2 GT - in any event, I can't
- > readily get rid of them, and re-installation isn't a viable option at the
- > moment.
- >
- > When XENIX tries to write to one of the bad sectors (it is always the same
- > one, 2162, which causes this problem, as far as I've noticed to date), and
- > an error message is produced, the inodes used percentage always jumps to
- > 100% - from what it actually is, i.e. 20-30% on average.
-
- I don't what kind of disk drive it is, but you might try this, if you
- have a 154x host adapter; Get a hold of SCSICNTL.EXE and see if the
- drive will accept the "Automatic Write Reallocation" setting under the
- error recovery page option. If the drive will accept this option, set
- it and reboot the system. The next time a write to the bad sector occurs,
- the driver *should* automatically map it out without the OS knowing about
- it.
- ---
-
- Roy Neese
- Adaptec Senior UNIX/SCSI Software Engineer
- UUCP: convex!egsner!adaptex!neese
- Inet: neese%adaptex@cirr.com
-