Jeff Wasilko <jeffw@smoe.org>
Satish Somanath <satish@lvision.com>
Sanjay Patel <patesa@aur.alcatel.com>
John Ballard <johnb@ocean.washington.edu>
Derek Cameron <Derek_Cameron@eagle.co.nz>
Marina Daniels <Marina.Daniels@ccd.tas.gov.au>
Jim Harmon <jharmon@telecnnct.com>
I choose Sanjay's response as a representative of most because it is the
most comprehensive, IMHO.
From: Sanjay Patel <patesa@aur.alcatel.com>
To: jjah@sol.ccsf.cc.ca.us
Cc:Sanjay <sanjay@aur.alcatel.com>,
Ellen Spoonamore <ellen@aur.alcatel.com>
Subject: Re: fsck
The file system state becomes "dirty" when you mount a file system.
thats how fsck knows that a system was not unmounted correctly.
ie: when you mount a file system, the file system becomes
"dirty"
when you unmount a file system, the file system becomes
"clean"
so, if the box goes down without unmounting all of the local file systems,
then fsck sees the "dirty" states and attempts to clean them up upon
reboot. so, all mounted file systems appear "dirty" when you fsck a
system that has locally mounted file systems. hense, that message will
never go away and you should not attempt to fix it.
if you check, the files systems are probably "/" and "/usr" (the
neccessary file systems for solaris)
>
> Hi Folks,
>
> This morning my Solaris 2.5 box crashed; I brought it up and ran fsck and
> fixed several problems, but a problem on two of my file systems persist:
> When the system comes up it does not complain about any file system
> problem, but when I run fsck I get:
> FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX?
> and I reply yes. It finishes; I reboot; the system comes up clean; I run
> fsck and get the same darn message.
>
> I appreciate any pointers to the solution.
Joe
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jjah@sol.ccsf.cc.ca.us