From: Akinobu Mita <akinobu.mita@gmail.com>
To: Don Mullis <dwm@meer.net>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, akpm <akpm@osdl.org>
Subject: Re: [PATCH -mm] fault-injection: reject-failure-if-any-caller-lies-within-specified range
Date: Tue, 21 Nov 2006 04:52:08 +0900 [thread overview]
Message-ID: <20061120195208.GA18077@APFDCB5C> (raw)
In-Reply-To: <1164050662.2912.55.camel@localhost.localdomain>
On Mon, Nov 20, 2006 at 11:24:22AM -0800, Don Mullis wrote:
> > This test is a little intentional.
> > (Normal I/O may fail, but journal commit I/O doesn't fail)
>
> I'm not sure in what sense the test could be called "intentional".
Because make_fault_request just injects failures randomly. there is no
difference between normal I/O and journal commit I/O.
The problem is the make_fault_request doesn't have clever setting such as
md/faulty module can simulate broken sectors.
> The patch raises the default stacktrace-depth from 10 to 32, and
> although there is indeed no guarantee this is enough, in practice I
> found the filesystem became hopelessly scrambled before ever hitting one
> of the kjournald cases again.
You can set /debug/fail_make_request/times smaller value so that
you can see what happened in filesystem before kjournald hits failure.
prev parent reply other threads:[~2006-11-20 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 17:45 [patch 0/7] Fault-injection capabilities (v6) Akinobu Mita
2006-11-20 3:04 ` [PATCH -mm] fault-injection: reject-failure-if-any-caller-lies-within-specified range Don Mullis
2006-11-20 10:57 ` Akinobu Mita
2006-11-20 19:24 ` Don Mullis
2006-11-20 19:52 ` Akinobu Mita [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=20061120195208.GA18077@APFDCB5C \
--to=akinobu.mita@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dwm@meer.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