From: Andreas Dilger <adilger@clusterfs.com>
To: Ed Sweetman <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-critical ext3-fs errors and IDE issues with 2.4.19-rc3
Date: Wed, 24 Jul 2002 17:01:27 -0600 [thread overview]
Message-ID: <20020724230127.GE574@clusterfs.com> (raw)
In-Reply-To: <1027469995.496.6.camel@psuedomode>
On Jul 23, 2002 20:19 -0400, Ed Sweetman wrote:
> On Tue, 2002-07-23 at 16:48, Andreas Dilger wrote:
> > Well, this is an error, and the next time the computer is restarted it
> > should force a full fsck on the partition. The other "panic" (oops)
> > situations are when things are totally shot and it is better to stop
> > doing anything than try and continue. In this case, it is possible to
> > continue, but that doesn't mean things are OK.
>
> I rebooted after setting max mount count to 1 so it would force an fsck.
That is not the right thing to do, FYI. That will mean that each time
you boot (even after clean shutdown) you will get an fsck. Instead,
you should change the mount count (-C), or the time it was last checked
(-T on more recent tune2fs) to force it to fsck. That will make it a
one-time event.
Yes, you could also touch /forcefsck or whatever, but that would force
it for all filesystems, again probably not what you want.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
prev parent reply other threads:[~2002-07-24 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 20:28 non-critical ext3-fs errors? Ed Sweetman
2002-07-23 20:48 ` Andreas Dilger
2002-07-24 0:19 ` non-critical ext3-fs errors and IDE issues with 2.4.19-rc3 Ed Sweetman
2002-07-24 23:01 ` Andreas Dilger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020724230127.GE574@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@speakeasy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox