From: Dave Wilson (dave.wilson at domain heanet.ie)
Date: Thu 03 Feb 2000 - 11:33:03 GMT
> why does my system on boot up give the error of maximal mount reached
> and then force a check of partitions hda3, hda5, hda6 even when theres
> plenty of space, as you can see from df...
It's not referring to disk space. Linux will generally force an fsck
under the following conditions:
* A partition wasn't unmounted cleanly
* It's been a long time since this partition was checked
* A partition has been mounted, cleanly, many times since the last fsck
("maximal mount count")
You should only get this message on occasional boots; if you get it
every time, something's wrong.
Dave
-- dave.wilson at domain heanet.ie --------------------------------------- +353-1-662-3412 It is one thing to pray; it is another to pray to entities who might not only be listening, but who will search you out on the road and beat you across the head with sticks if you say something that offends them. -- Neil Gaiman ------------------ For crypto key send a blank message to davew+pgp at domain heanet.ie
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:05:21 GMT