I do appreciate all the help though. This is how "newbies" learn.
Regards,
--Steve
> From aeb@cwi.nl Wed Mar 13 04:13:45 1996
> Date: Wed, 13 Mar 1996 10:06:33 +0100
> From: Andries.Brouwer@cwi.nl
> To: cahill@skipper.icd.teradyne.com, linux-kernel@vger.rutgers.edu
> Subject: Re: Filesystem state: not clean
> Content-Length: 589
>
> Steve Cahill:
>
> : dumpe2fs --> says my Linux partitions (/dev/sda2 and /dev/sda3) are
> : "not clean".
>
> : I.E. --> Filesystem state: not clean
>
> : 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 (perhaps I should
> : force checking with boot parameters?).
>
> Ach - all these newbies filling up the kernel channel...
> This belongs in comp.os.linux.setup or so.
> The answer is: nothing is wrong - don't worry - a mounted filesystem
> is by definition not clean.
>
> From pfnguyen@netcom22.netcom.com Wed Mar 13 02:10:19 1996
> Date: Tue, 12 Mar 1996 15:57:50 -0800 (PST)
> From: Perry F Nguyen <pfnguyen@netcom22.netcom.com>
> Reply-To: pfnguyen@netcom.com
> To: Steve Cahill <cahill@skipper.icd.teradyne.com>
> Cc: aic7xxx@freebsd.org, linux-scsi@vger.rutgers.edu,
> linux-kernel@vger.rutgers.edu, smc@empire.net
> Subject: Re: Filesystem state: not clean with AHA2940W AIC7870
> Return-Receipt-To: pfnguyen@netcom.com
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset="US-ASCII"
> Content-Length: 4790
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Tue, 12 Mar 1996, Steve Cahill wrote:
>
> > Folks,
> > dumpe2fs --> says my Linux partitions (/dev/sda2 and /dev/sda3) are
> > "not clean".
>
> > I.E. --> Filesystem state: not clean
> Mounting will cause the filesystem state to become "not clean", that way
> if a crash were to occur, fsck will force the filesystem check upon the
> next boot. If it were clean, a crash will leave the filesystems in the
> clean state, and therefore skip fsck.
>
> Umounting will change the clean flag to clean, and it will no longer be
> unclean.
>
> > During boot-up everything appears normal and Linux partitions are
> > reported as "clean" so "no checking" is executed (perhaps I should
> > force checking with boot parameters?).
>
> It _is_ *normal*.
>
> > Only when I login and actually execute dumpe2fs do I get this report of
> > unclean filesystem.
>
> > One of my Linux colleagues suggested a reinstall with no DOS partitions
> > 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. I think the drive is starting to wear out a little from
> > being reformatted so many times :)
>
> Don't listen to your colleague :-)
>
> > Is it safe to run e2fsck with Linux (active) partitions mounted?
> Safe only if mounted read-only
>
> > Are there ways to determine why my filesystem is not clean and what
> > might be causing it?
>
> It's unclean because of mounting -- (see example below).
>
> > Am I needlessly worrying as everything appears stable with no crashes
> > or hanging?
>
> Yes, you are needlessly worrying.
>
> > Regards and Thanks in advance,
>
> You're welcome.
>
> > 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.
>
> Example: (Yes, this is off a true filesystem :-)
> # df /dev/sda6
> Filesystem 1024-blocks Used Available Capacity Mounted on
> /dev/sda6 100118 84700 10248 89% /usr/src
> # tune2fs -l /dev/sda6
> tune2fs 1.02, 16-Jan-96 for EXT2 FS 0.5b, 95/08/09
> Filesystem magic number: 0xEF53
> Filesystem state: not clean
> Errors behavior: Continue
> Inode count: 25896
> Block count: 103408
> Reserved block count: 5170
> Free blocks: 15418
> Free inodes: 18420
> First block: 1
> Block size: 1024
> Fragment size: 1024
> Blocks per group: 8192
> Fragments per group: 8192
> Inodes per group: 1992
> Last mount time: Tue Mar 12 15:26:54 1996
> Last write time: Tue Mar 12 15:30:03 1996
> Mount count: 9
> Maximum mount count: 20
> Last checked: Fri Mar 8 15:13:42 1996
> Check interval: 0
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> # umount /dev/sda6
> # df /usr/src
> Filesystem 1024-blocks Used Available Capacity Mounted on
> /dev/sda2 298381 106588 176382 38% /usr
> # tune2fs -l /dev/sda6
> tune2fs 1.02, 16-Jan-96 for EXT2 FS 0.5b, 95/08/09
> Filesystem magic number: 0xEF53
> Filesystem state: clean
> Errors behavior: Continue
> Inode count: 25896
> Block count: 103408
> Reserved block count: 5170
> Free blocks: 15418
> Free inodes: 18420
> First block: 1
> Block size: 1024
> Fragment size: 1024
> Blocks per group: 8192
> Fragments per group: 8192
> Inodes per group: 1992
> Last mount time: Tue Mar 12 15:26:54 1996
> Last write time: Tue Mar 12 15:30:03 1996
> Mount count: 9
> Maximum mount count: 20
> Last checked: Fri Mar 8 15:13:42 1996
> Check interval: 0
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> # mount /usr/src
> Filesystem 1024-blocks Used Available Capacity Mounted on
> /dev/sda6 100118 84700 10248 89% /usr/src
> #
>
> End Example
>
>
> PS: tune2fs -l will provide the same effect as dumpe2fs without
> dumping inode group information and such.
>
> - --
> | pfnguyen@netcom.com - ftp://ftp.netcom.com/pub/pf/pfn | TCP/IP Networking, |
> | 1024/0D97E00D 1995/01/01 Perry "Huy" Francis Nguyen | Unix Systems Admin, |
> | CE 62 F2 01 33 87 9D 89 - BC 53 8D 11 F9 A0 DE 8F | and Consulting. |
> | FTP, finger or mail with subject PGPKEY for PGP Key | Applications Devel. |
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBMUYPeS2IFwkNl+ANAQHKBQP/anAgBPa36uYCHVfugClI6WZGHTNIpsHV
> 6/DiKmTOzm1auFGsKZjJU9CFIeAg6flMy4lqKjUNZug0pIFN+zpSUuTmZNKtz0fI
> fYnlx6GbUPL/4tHDEl8bmgoVyiciPmcC6ylPHnVlSO9zBmZcL+nBH1GrWkejNZ6J
> /F2tqmANYnE=
> =uUcs
> -----END PGP SIGNATURE-----