From: Jeff Mahoney <jeffm@suse.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [PATCH] ReiserFS v3 I/O error handling
Date: Wed, 15 Sep 2004 10:30:56 -0400 [thread overview]
Message-ID: <41485220.7050602@suse.com> (raw)
In-Reply-To: <20040915141202.GF5137@backtop.namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alex Zarochentsev wrote:
|> I assume that was tested with some simulated i/o errors, wasn't it?.
Of course. The debugging code is since removed, but every place there
was a !buffer_uptodate(bh) check, I added a trigger such that I could
trigger each error path individually. I triggered various error paths
while running fsx, stress.sh, and/or ltp's fsstress.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBSFIfLPWxlyuTD7IRAqljAKCoCuXGN4GSG+hQ2RuiSNtuMZSVuwCgnEMp
gQhDrTbctbjBYwD8U73EB5E=
=2OFI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-15 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 22:11 [PATCH] ReiserFS v3 I/O error handling Jeff Mahoney
2004-09-15 13:11 ` Alex Zarochentsev
2004-09-15 13:47 ` Jeff Mahoney
2004-09-15 14:12 ` Alex Zarochentsev
2004-09-15 14:30 ` Jeff Mahoney [this message]
2004-09-15 14:31 ` Hans Reiser
2004-09-21 17:46 ` Chris Mason
2004-09-22 15:39 ` Hans Reiser
2004-09-22 16:52 ` Alex Zarochentsev
-- strict thread matches above, loose matches on Subject: below --
2004-09-14 15:39 Jeff Mahoney
2004-09-15 1:26 ` Hans Reiser
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=41485220.7050602@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@namesys.com \
/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.