From TFarrell@fallschurch.esys.com Mon Apr 10 20:05:31 2000
From: TFarrell@fallschurch.esys.com
To: users@lists.opensuse.org
Subject: RE: [SLE] maximal mount count
Date: Mon, 10 Apr 2000 16:05:31 -0400
Message-ID:
<287EE132D8F1D3119C4500E0291A7D8730C3C8@xchange01.isg.fcd.esys.com>
In-Reply-To: <[SLE] maximal mount count>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7546098317651623821=="
--===============7546098317651623821==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
> What does this mean and why does it happen?
Ok, I'll take a stab at this one. Take this as a best of my knowledge
explanation. The ext2 filesystem keeps track of the status of the filesystem
in a field within the superblock. This can have a "clean" or "unclean" state
depending on how it was unmounted. There is ext2 kernal code that maintains
this state. In addition to this state field within the superblock, the ext2
filesystem has two methods of forcing checks of the f/s at regular
intervals. There is also a counter in the superblock which is incremented on
each read/write mount. If it reaches the maximum value (set with tun2efs) or
the time interval has been exceeded a check is forced. In short it is by
design. I couldn't really tell what the effects would be of changing the
maximal mount count or the check interval but I wouldn't recommend it. <:
If there is any inaccuracies in this explanation please don't hesitate to
correct them.=20
Thom
RE: [SLE] maximal mount count
> What does this mean and why does it happen?
Ok, I'll take a stab at this one. Take this as a best of my kn=
owledge explanation. The ext2 filesystem keeps track of the status of the fil=
esystem in a field within the superblock. This can have a "clean" or "unclean=
" state depending on how it was unmounted. There is ext2 kernal code that mai=
ntains this state. In addition to this state field within the superblock, the=
ext2 filesystem has two methods of forcing checks of the f/s at regular inte=
rvals. There is also a counter in the superblock which is incremented on each=
read/write mount. If it reaches the maximum value (set with tun2efs) or the =
time interval has been exceeded a check is forced. In short it is by design. =
I couldn't really tell what the effects would be of changing the maximal moun=
t count or the check interval but I wouldn't recommend it. <:
If there is any inaccuracies in this explanation please don't =
hesitate to correct them.
Thom
--===============7546098317651623821==--