public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ext3: bump mount count on journal replay
Date: Wed, 14 Jul 2004 15:55:26 -0400	[thread overview]
Message-ID: <20040714195526.GF3229@thunk.org> (raw)
In-Reply-To: <20040714131525.GA1369@elf.ucw.cz>

On Wed, Jul 14, 2004 at 03:15:25PM +0200, Pavel Machek wrote:
> 
> Currently, you get fsck "just to be sure" once every ~30 clean
> mounts or ~30 hard shutdowns. I believe that hard shutdown is way more
> likely to cause some disk corruption, so it would make sense to fsck
> more often when system is hit by hard shutdown.
> 

At least in theory an unclean shutdown is not going to cause any
problems, unless the hardware is screwy, in which case even a single
hard shutdown is going to cause problems.  I'm not sure that it really
makes sense to arbitrarily state that a hard shutdown is 5 times more
likely to cause problems.  We could make it be configurable, I
suppose, but I'm not sure it's worth it to add all that extra
complexity.  (Heck, we could also argue using a similar reasoning that
software suspends also increases the chances of filesystem corruption
"if something bad happens".  :-)

						- Ted

  reply	other threads:[~2004-07-14 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 13:15 ext3: bump mount count on journal replay Pavel Machek
2004-07-14 19:55 ` Theodore Ts'o [this message]
2004-07-14 20:30   ` Pavel Machek
2004-07-14 20:05 ` Andreas Dilger
2004-07-14 20:32   ` Pavel Machek
2004-07-16 20:41     ` [Ext2-devel] " Andreas Dilger
2004-07-16 21:06       ` Pavel Machek

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=20040714195526.GF3229@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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