From: Hans Reiser <reiser@namesys.com>
To: Jeffrey Mahoney <jeffm@novell.com>
Cc: Alex Zarochentsev <zam@namesys.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] I/O Error Handling for ReiserFS v3
Date: Tue, 05 Oct 2004 10:40:58 -0700 [thread overview]
Message-ID: <4162DCAA.50902@namesys.com> (raw)
In-Reply-To: <20041005172233.GE28617@backtop.namesys.com>
Alex Zarochentsev wrote:
>On Tue, Oct 05, 2004 at 08:44:22AM -0700, Hans Reiser wrote:
>
>
>>These have received design approval from zam (and thus me), but zam, did
>>they receive stress testing by Elena under your guidance?
>>
>>
>
>No. We have a long queue of test tasks. There are fsck.reiser4 testing,
>reiser4/dmapper crashes and the benchmarks in the queue.
>
>
Well, we cannot let our process be a barrier to good patches getting in,
so let me ask, Jeff, did you test each of these conditions you
improved? How? Did anyone else test them?
>
>
>>Hans
>>
>>Jeffrey Mahoney wrote:
>>
>>
>>
>>>Hey all -
>>>
>>>One of the most common complaints I've heard about ReiserFS is how graceless
>>>it is in handling critical I/O errors.
>>>
>>>ext[23] can handle I/O errors anywhere, with the results being up to the
>>>system admin to determine: continue, go read only, or panic.
>>>
>>>ReiserFS doesn't offer the admin any such choice, instead panicking on any
>>>I/O error in the journal.
>>>
>>>The available options are read only or panic, since ReiserFS does not
>>>currently support operations without the journal.
>>>
>>>In the four messages that follow, you'll find: *
>>>reiserfs-cleanup-buffer-heads.diff - Cleans up handling of buffer head
>>>bitfields - uses the kernel supplied FNS_BUFFER macros instead. *
>>>reiserfs-cleanup-sb-journal.diff - Cleans up accessing of the journal
>>>structure, prefering to create a temporary variable in functions that access
>>>the journal structure non-trivially. Should make 0 difference at compile
>>>time. * reiserfs-io-error-handling.diff - Allows ReiserFS to gracefully
>>>handle I/O errors in critical code paths. The admin has the option to go
>>>read-only or panic. Since ReiserFS has no option to ignore the use of the
>>>journal, the "continue" method is not enabled. * reiserfs-write-lock.diff -
>>>Fixes two missing reiserfs_write_unlock() calls on error paths that are
>>>unrelated to reiserfs-io-error-handling.diff
>>>
>>>These patches have seen a lot of testing in the SuSE Linux Enterprise Server
>>>9 kernel, and are considered ready for mainline.
>>>
>>>They've received approval[1] from the ReiserFS maintainers also.
>>>
>>>Andrew - Apologies for the previous format; Please apply.
>>>
>>>Thanks.
>>>
>>>-Jeff
>>>
>>>[1] http://marc.theaimsgroup.com/?l=reiserfs&m=109587254714180
>>>
>>>-- Jeff Mahoney SuSE Labs
>>>
>>>
>>>
>>>
>
>
>
next prev parent reply other threads:[~2004-10-05 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 15:08 Jeffrey Mahoney
2004-10-05 15:44 ` Hans Reiser
2004-10-05 17:22 ` Alex Zarochentsev
2004-10-05 17:40 ` Hans Reiser [this message]
2004-10-05 18:21 ` Jeff Mahoney
2004-10-05 18:40 ` Hans Reiser
2004-10-05 15:45 ` 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=4162DCAA.50902@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=jeffm@novell.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome