From: Andreas Dilger <adilger@clusterfs.com>
To: Daniel Drake <ddrake@brontes3d.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck and human intervention
Date: Wed, 7 Mar 2007 13:19:13 +0800 [thread overview]
Message-ID: <20070307051913.GF5723@schatzie.adilger.int> (raw)
In-Reply-To: <1173191227.11804.9.camel@systems03.mmm.com>
On Mar 06, 2007 09:27 -0500, Daniel Drake wrote:
> OK. Given that write caching may be required for performance reasons or
> there might be other possible reasons which would result in
> preen-unrepairable fs corruption on power loss, my question is now: Is
> it a really bad idea to run "e2fsck -y" on every boot?
If your primary concern is not halting the boot, then yes. 99% of people
only know to answer "y" to e2fsck anyways.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2007-03-07 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 16:26 e2fsck and human intervention Daniel Drake
2007-03-05 16:48 ` Theodore Tso
2007-03-05 17:01 ` Daniel Drake
2007-03-05 17:42 ` Sev Binello
2007-03-06 2:40 ` Andreas Dilger
2007-03-06 14:27 ` Daniel Drake
2007-03-07 5:19 ` 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=20070307051913.GF5723@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=ddrake@brontes3d.com \
--cc=linux-ext4@vger.kernel.org \
/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