From: Paul Mc Auley (paul at domain baltimore.ie)
Date: Thu 03 Feb 2000 - 11:42:38 GMT
On Thu, 3 Feb 2000 11:34:13 +0000 (GMT)
Leo Talbot <leo at domain maths.tcd.ie> wrote:
| On Thu, 3 Feb 2000, Dermot Gorman wrote:
| > 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...
| The mount count has nothing got to do with the space left on the partitions,
| it has to do with the number of times that partition has been mounted.
| After every X mountings (not sure what X is...its about 20...I think), the
| system runs fsck on the partition to make sure that everything's alright.
| I'm not sure if X can be changed or not...
It can, using tune2fs. This is particularly useful if you are using a laptop
(which goes through the boot cycle rather more often). The drill is to bring
the machine up in single user mode and "tune2fs -c <number> /dev/<partition>"
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:05:21 GMT