From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jakob Oestergaard <jakob@unthought.net>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>
Subject: Re: jbd bug(s) (?)
Date: Thu, 26 Sep 2002 13:27:23 +0100 [thread overview]
Message-ID: <20020926132723.D2721@redhat.com> (raw)
In-Reply-To: <20020926122124.GS2442@unthought.net>; from jakob@unthought.net on Thu, Sep 26, 2002 at 02:21:24PM +0200
Hi,
On Thu, Sep 26, 2002 at 02:21:24PM +0200, Jakob Oestergaard wrote:
> Originally it was my impression that the index was written fairly
> frequently, *and* that you did not have the atomic-sector-write
> guarantee.
The index is only updated when we purge stuff out of the journal.
That can still be quite frequent on a really busy journal, but it's
definitely not a required part of a transaction.
That's deliberate --- the ext3 journal is designed to be written as
sequentially as possible, so seeking to the index block is an expense
which we try to avoid.
> RAID wouldn't save me in the case where the journal index is screwed due
> to a partial sector write and a power loss.
A partial sector write is essentially impossible. It's unlikely that
the data on disk would be synchronised beyond the point at which the
write stopped, and even if it was, the CRC would be invalid, so you'd
get a bad sector error return on subsequent attempts to read that data
--- you'd not be given silently corrupt data.
Making parts of the disk suddenly unreadable on power-fail is
generally considered a bad thing, though, so modern disks go to great
lengths to ensure the write finishes.
--Stephen
next prev parent reply other threads:[~2002-09-26 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 7:21 jbd bug(s) (?) Jakob Oestergaard
2002-09-25 16:36 ` Stephen C. Tweedie
2002-09-26 12:21 ` Jakob Oestergaard
2002-09-26 12:27 ` Stephen C. Tweedie [this message]
2002-09-26 12:56 ` Jakob Oestergaard
2002-09-26 13:44 ` Theodore Ts'o
2002-09-26 14:05 ` Christoph Hellwig
2002-09-26 14:25 ` Theodore Ts'o
2002-09-26 14:41 ` Christoph Hellwig
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=20020926132723.D2721@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=jakob@unthought.net \
--cc=linux-kernel@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