Message-ID: <4162C156.3030108@namesys.com>
Date: Tue, 05 Oct 2004 08:44:22 -0700
From: Hans Reiser <reiser@namesys.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
MIME-Version: 1.0
To: Jeffrey Mahoney <jeffm@novell.com>
CC: Andrew Morton <akpm@osdl.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Alexander Zarochentcev <zam@namesys.com>
Subject: Re: [PATCH 0/4] I/O Error Handling for ReiserFS v3
References: <20041005150819.GA30046@locomotive.unixthugs.org>
In-Reply-To: <20041005150819.GA30046@locomotive.unixthugs.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2237
Lines: 63

These have received design approval from zam (and thus me), but zam, did 
they receive stress testing by Elena under your guidance?

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
>  
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/