Clarification, it will fsck the drive. it will not however say "maximal
mount count reached" it will say something totaly different, "/dev/XXX was
not cleanly unmounted check forced" to be specific..
On Tue, 12 Oct 1999, Bois, Mathieu wrote:
> It also happens the next time you reboot, if you exit from Linux without
> unmounting the partitions (typicly, in the case of a power outage).
>
> Mathieu
>
> > -----Original Message-----
> > From: Ken Wilson [mailto:[EMAIL PROTECTED]]
> > Sent: 12 October 1999 04:57
> > To: [EMAIL PROTECTED]
> > Subject: RE: [expert] maximal mount count?
> >
> >
> > It's a routine check. All your Linux partitions will get this check
> > after they've been mounted x number of times. It checks for
> > fragmentation and other disk ailments and attempts to correct the
> > situation.
> >
> > Ken Wilson
> > First Law of Optimisation: The speed of a non-working program is
> > irrelevant
> > (Steve Heller, 'Efficient C/C++ Programming')
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of David van Balen
> > Sent: Monday, October 11, 1999 7:51 PM
> > To: [EMAIL PROTECTED]
> > Subject: [expert] maximal mount count?
> >
> >
> >
> > I just booted my machine and got the message: "/dev/hdb1 has reached
> > maximal mount count, check forced" after which linux
> > proceeded to run a
> > check that lasted several minutes.
> > Does this indicate a problem? Or is it just a routine check? If so,
> > what's
> > it checking for?
> >
> >
> > DvB
> >
> >
> >
>
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
