Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!nosc!humu!pegasus!pilikia!art
From: art@pilikia.pegasus.com (Art Neilson)
Newsgroups: comp.unix.questions
Subject: Re: Recurring problem in root filesystem
Message-ID: <1990Sep04.175054.17770@pilikia.pegasus.com>
Date: 4 Sep 90 17:50:54 GMT
References: <1990Aug31.134539.749@aucs.uucp> <1990Sep02.232056.9063@pilikia.pegasus.com> <4010@auspex.auspex.com>
Organization: Pilikia, Honolulu
Lines: 14

In article <4010@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>>Try running fsck on the *unmounted* root filesystem,
>
>Try unmounting the root filesystem first.  Good luck....

What do you mean, good luck??  I've run fsck on the unmounted hard disk
root filesystem on my system here, just boot with your disaster disk
and away you go ;^).  It's not impossible.  Besides, the point I was making
was that the message he was getting was *probably* due to his running
fsck on the mounted root file system.  The wrong inode count will always
occur because of the scratch file fsck creates.
-- 
Arthur W. Neilson III		| ARPA: art@pilikia.pegasus.com
Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pegasus!pilikia!art