On 20-Apr-98 David Reed wrote:
>
> When booting up (running 4.2 with kernel 2.0.32-1.2)
> I get a message about some mount count being exceeded, and needing to run
> e2fsck. Now if I remember correctly, it used run auto-majically at that
> point in the boot sequence...
>
> So, how do I get ti back to that state?
>
> What is likely to have happened that changed this behavior?
>
> if possible, please email me directly (copy list if you choose to),
> as I am frequently dropping the list due to bandwidth constraints.
If it's the main partition, the one with root on it, it should still be
auto-fixed at boot unless you changed it in the boot scripts (located in
/etc/rc.d/rc.sysinit). Other partitions will not get checked automatically
unless you add the call to them yourself.
One way: unmount the partition, run fsck on it, then remount it.
Another way: change the settings in fstab so they aren't automounted and add
lines to /etc/rc.d/rc.local to run fsck on boot and then mount the
partitions afterward. Something like the following:
fsck /dev/sda1
fsck /dev/sda2
fsck /dev/sdb1
fsck /dev/sdc1
mount /dev/sda1
.....etc....
This placed right at the end stopped me from having to go thru the messages
and see which needed to be cleaned and then having to take them down to
fsck them.
One little caveat: if all partitions reach maximum at the same time, you
could wait days (a slight exaggeration - it only feels like days) to make
them go thru the process. I simply mounted and umounted them different
numbers of times to make sure the quota came at different boot periods.
That way no more than one partition has to go thru the entire fix process
at each boot.
---
A prune isn't a vegetable; a cabbage is a vegetable.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
