EXT3-fs warning:?

[Ralph Crongeyer]

On Friday 23 May 2003 10:53 am, Ralph Crongeyer wrote:

Ok, I found the problem.
In the /etc/init.d/mount script there is a line that reads:

"fsck -A -y -a &> /dev/null"

The options -A -y -a will not work together (at least not on my system).
The -A option is for walking through the fstab file to repair all the 
filesystems. The -y option tells fsck to assume yes to all questions. The -a 
option means automatically repair the file system. So using -y and -a with -A 
does not work. If you edit the /etc/init.d/mount script and remove the -a 
option and save it you will see that it will indeed check the file system 
during boot.

Maby this should be fixed in the module it comes from.

Ralph 

> On Thursday 22 May 2003 06:09 pm, Terry Chan wrote:
>
> Terry,
>
> Thanks for the reply.
>
> > And NO this cannot be done automatically during the boot process from
> > your regular lunar hard drive install.
>
> WHY??
>
> Is this just a problem with Lunar Linux??
> Because all other linux distros I have used are able to run e2fsck DURING
> BOOT. If you look at the man page for fstab (here is a snipit from the man
> page):
>
>      The sixth field, (fs_passno), is used by the fsck(8) program to
> determine the order in which filesystem checks are done at reboot time. 
> The root filesystem should be specified with a fs_passno of 1, and other
> filesys- tems should have a fs_passno of 2.  Filesystems within a drive
> will be checked sequentially, but filesystems on different drives will be
> checked at the same time to utilize parallelism available in the hardware. 
> If the sixth field is not present or zero, a value of zero is returned and
> fsck will assume that the filesystem does not need to be checked.
>
> Note the first line "done at reboot time.".
>
> I have the sixth field set to 1 in fstab yet my system will not run the
> e2fsck checks.
>
> Anybody know how to set this up?
>
> Ralph
>
> > Ralph,
> >
> > As also stated in this list before, you have to:
> >
> > 1. Boot your linux box with a linux boot floppy or preferably the
> > Lunar Install/Rescue cdrom.
> >
> > 2. With your ext3 partition UNMOUNTED, run from the shell prompt
> >   e2fsck /dev/hda3
> > or if for some reason that notation doesn't work you can use
> >   e2fsck /dev/discs/disc0/part3
> >
> > 3. Reboot from your hard drive after finishing the file system check.
> >
> > And NO this cannot be done automatically during the boot process from
> > your regular lunar hard drive install.
> >
> > Terry Chan
> > ---------------------------------------------------------------------
> >
> > On Thu, May 22, 2003 at 05:29:55PM -0400, rcrongeyer at rpicc.com wrote:
> > > Hi all,
> > >
> > > I know I have posted a message about this on the list before but I have
> > > yet to figure it out. I am getting this warning during boot up:
> > > EXT3-fs warning: maximal mount count reached, running e2fsck is
> > > recommended
> > >
> > > I seens that the file system is being mounted in ordered data mode
> > > before e2fsck is able to run. Everything is currently up to date. Here
> > > is a snipit of my dmesg:
> > >
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > VFS: Mounted root (ext3 filesystem) readonly.
> > > Freeing unused kernel memory: 104k freed
> > > Adding Swap: 489972k swap-space (priority -1)
> > > EXT3-fs warning: maximal mount count reached, running e2fsck is
> > > recommended EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,3), internal
> > > journal NTFS: Warning! NTFS volume version is Win2k+: Mounting
> > > read-only
> >
> > _______________________________________________
> > Lunar mailing list
> > Lunar at lunar-linux.org
> > http://lunar-linux.org/mailman/listinfo/lunar
>
> _______________________________________________
> Lunar mailing list
> Lunar at lunar-linux.org
> http://lunar-linux.org/mailman/listinfo/lunar