From: Simon Kirby <sim@netnation.com>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: status of the ext3/jbd error handling enhancement patches
Date: Mon, 20 Oct 2008 10:17:12 -0700 [thread overview]
Message-ID: <20081020171712.GA22653@hostway.ca> (raw)
In-Reply-To: <48FC081D.60306@hitachi.com>
On Mon, Oct 20, 2008 at 01:25:01PM +0900, Hidehiro Kawai wrote:
> Hi Andrew,
>
> Thank you for pushing my ext3/jbd to Linus. But some of patches
> in -mm (following three patches) haven't been sent to Linus.
>
> #jbd-fix-error-handling-for-checkpoint-io.patch: double-check this
> jbd-fix-error-handling-for-checkpoint-io.patch
> ext3-add-checks-for-errors-from-jbd.patch
> jbd-test-bh_write_eio-to-detect-errors-on-metadata-buffers.patch
>
> They improve filesystem corruption problem and it is needed by
> mission critical systems.
Hi Hidehiro,
It seems you have been looking the code behind the problems I reported
(see linux-ext4 post "EXT3 way too happy with write errors", October
14th).
Are you aware of any patches that look at failed writes outside of JBD
also not noticing write errors? It seems that not all write errors are
causing EXT3 to take the action of aborting the journal, which seems to
be a very bad idea (an example in my previous posting, testing with fault
injection).
Anyway, I would be very happy to test out any patches in this area, and
if none exist, I will try to track down why it is ignoring some of these
errors.
Thanks,
Simon-
next prev parent reply other threads:[~2008-10-20 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 4:25 status of the ext3/jbd error handling enhancement patches Hidehiro Kawai
2008-10-20 5:13 ` Andrew Morton
2008-10-20 12:41 ` Theodore Tso
2008-10-21 6:24 ` Hidehiro Kawai
2008-10-21 6:37 ` Andrew Morton
2008-10-20 17:17 ` Simon Kirby [this message]
2008-10-22 4:54 ` Hidehiro Kawai
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=20081020171712.GA22653@hostway.ca \
--to=sim@netnation.com \
--cc=hidehiro.kawai.ez@hitachi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.