> I have now completed my seventh Linux installation since mid December.
> Finally everything seems stable, but...
> I still have this one nagging issue:
> dumpe2fs --> says my Linux partitions (/dev/sda2 and /dev/sda3) are
> "not clean".
filesystems are only clean when not mounted (or mounted
read-only). Once the filesystem is mounted read-write, part
of it is almost always in memory, thus, it isn't clean. The
"clean" bit is set again when the fs is unmounted normally.
(All the buffers are flushed, etc., when "umount"ing.)
> I.E. --> Filesystem state: not clean
Perfectly normal on a mounted filesystem. In fact, if it
said it *was* clean, that would be wrong, because the
mechanism wouldn't be working correctly. It is
*necessarily* "not clean" when mounted.
> on either partition (/dev/sda2=root and /dev/sda3=/usr) after login.
> During boot-up everything appears normal and Linux partitions are
> reported as "clean" so "no checking" is executed
Good, good.
> (perhaps I should
> force checking with boot parameters?).
(no.)
> Only when I login and actually execute dumpe2fs do I get this report of
> unclean filesystem.
Mounted filesystems aren't clean.
> One of my Linux colleagues suggested a reinstall with no DOS partitions
I'm surprised. I thought everyone understood the "clean"
flag.
> on the drive (but should this matter with SCSI?). I thought it best to
> strobe a couple of newsgroups to see if anyone else might be
> experiencing anything similiar and if I could get some alternate
> suggestions.
> A while back (before I physically looked at my controller) I was very
> concerned when I learned that the AIC7850 chipset which is _not_ fully
> supported yet, thinking this was my problem. It was a relief to find my
> chipset is the AIC7870. I was getting suggestions to update my kernel
> to 1.3.68 or greater. Is this necessary with the AIC7870 chipset
> AHA2940W?
Well, obviously not, since it's working for you. But you
might want to do it anyway. I understand that there have
been many improvements to the code, and even though I'm not
sure what exactly they are, well, if something fails, at
least people won't tell me, "get the latest version."
> Is it safe to run e2fsck with Linux (active) partitions mounted?
NO! NO! NO! Do *not* run fsck on a filesystem mounted
read-write! This can lead to serious corruption!
> Are there ways to determine why my filesystem is not clean and what
> might be causing it?
It's not clean because it is in use.
> Am I needlessly worrying as everything appears stable with no crashes
> or hanging?
Yes. Or at least, you don't understand dumpe2fs. (or ext2,
or Unix filesystems in general.) I guess it's *okay* to
worry, if it motivates you to learn more. But don't try to
fix something until you're pretty sure it's broke.
> Suggestions are welcomed with open arms and open mind.
Read up on fsck, dumpfs, etc. in a Un*x system
administrators guide.
> Regards and Thanks in advance,
Happy Linuxing!
> cahill@icd.teradyne.com
> smc@empire.net
> ps: Please reply directly to either of the above addresses as I am not
> sure whether I am currently subscribed to any of the newsgroups you
> might be reading this from.
[done]
-- Michael J. Micek, peripatetic philosopher. Try 'em all (Mt 8:20) mmicek@nyx.net mmicek@muddcs.cs.hmc.edu Hi! sam@butthead.colorado.edu ab496@freenet.uchsc.edu