From: Andrew Morton <akpm@zip.com.au>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3: kjournald and spun-down disks
Date: Sun, 25 Nov 2001 19:34:29 -0800 [thread overview]
Message-ID: <3C01B845.33314F49@zip.com.au> (raw)
In-Reply-To: <3BFF06CA.71B99D3C@zip.com.au> <Pine.LNX.4.40.0111252110490.2207-100000@waste.org>
Oliver Xymoron wrote:
>
> Ok, so what's the theory behind the journal timer? Why would we want
> ext3 journal flushed more or less often than ext2 metadata given that
> they're of equivalent importance?
umm, err.. If your machine crashes, ext3 will restore its state
to that which pertained between zero and five seconds before the crash.
With ext2+fsck, things are not as clear. Your data will be restored
to that which pertained from zero to thirty seconds prior to crash.
inodes and superblock to that which pertained from zero to thirty
five seconds before the crash, stuff like that.
A five second window is short enough for you to be confident that
everything you want is still there. With thirty seconds, uncertainty
creeps in.
Yes, it needs to be configurable.
-
next prev parent reply other threads:[~2001-11-26 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 1:10 ext3: kjournald and spun-down disks Oliver Xymoron
2001-11-24 1:25 ` Andrew Morton
2001-11-24 1:58 ` Oliver Xymoron
2001-11-24 2:32 ` Andrew Morton
2001-11-26 3:15 ` Oliver Xymoron
2001-11-26 3:34 ` Andrew Morton [this message]
2001-11-26 15:22 ` Oliver Xymoron
2001-11-26 23:25 ` Daniel Kobras
2001-11-26 23:40 ` Andrew Morton
2001-11-27 0:18 ` Andreas Dilger
2001-11-27 0:03 ` Andre Hedrick
2001-11-27 0:21 ` Oliver Xymoron
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=3C01B845.33314F49@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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