Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!comix!jeffl
From: jeffl@comix.UUCP (Jeff Liebermann)
Newsgroups: comp.unix.xenix.sco
Subject: Re: fsck fails on /dev/root under SCO (was Re: fsck Recovery From Crashes)
Summary: Silent fsck exit
Keywords: inode file directory lost+found fsck sosco
Message-ID: <122@comix.UUCP>
Date: 6 Jun 91 08:16:12 GMT
References: <35@metran.UUCP> <1991Jun02.184143.15566@virtech.uucp> <3206@artcom0.north.de>
Organization: COmmittee to Maintain Independent Xenix
Lines: 24

In article <3206@artcom0.north.de> pf@artcom0.north.de (Peter Funk) writes:
>In <1991Jun02.184143.15566@virtech.uucp> 

[ good info on fsck deleted]

>In some rather rare situations the file system will end up in a state, 
>where following attempts with 'fsck' will exit during phase 1 without 
>any further error message (only the nonzero exit code indicates an error).
 
From SCO's sosco support fix xnx124....
-----------------------------------------------------------------------
The enclosed Support Level Supplement contains a new /bin/fsck which
solves problems experienced with fsck quitting silently under SCO XENIX
386 Operating System Releases 2.3.0, 2.3.1, or 2.3.3 for AT architecture
machines. It is engineered specifically for these releases of the Operating
System, and should not be installed on a system running a release other
than these.
-----------------------------------------------------------------------

-- 
# Jeff Liebermann   Box 272   1540 Jackson Ave     Ben Lomond    CA  95005
# 408.336.2558  voice           WB6SSY @ KI6EH.#NOCAL.CA.USA   packet radio
# 408.699.0483  digital pager   73557,2074       cis
# jeffl@comix.santa-cruz.ca.us  uunet!comix!jeffl  jeffl%comix@ucscc.ucsc.edu