All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [PATCH] ReiserFS v3 I/O error handling
Date: Wed, 15 Sep 2004 17:11:33 +0400	[thread overview]
Message-ID: <20040915131133.GD5137@backtop.namesys.com> (raw)
In-Reply-To: <41461B2F.7080100@suse.com>

Hi Jeff,

On Mon, Sep 13, 2004 at 06:11:59PM -0400, Jeff Mahoney wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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.
> 
> Attached are four patches, against 2.6.9-rc2:
> * reiserfs-cleanup-buffer-heads.diff
> 	- Cleans up handling of buffer head bitfields - uses
> 	  the kernel supplied FNS_BUFFER macros instead.
ok

> * 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.
ok

> * reiserfs-write-lock.diff
> 	- Fixes two missing reiserfs_write_unlock() calls on error paths
> ~          that are unrelated to the last patch.
ok

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

What reiserfs will do with already dirty blocks on the R/O fs.  Those blocks
remain dirty, yes?

The whole patch is enough complex, one look is not enough :) I think Elena may
do additional testing to be sure that nothing is broken while improving i/o
handling. 

> These patches have seen a lot of testing in the SuSE Linux Enterprise
> Server 9 kernel, and are considered ready for mainline.
> 
> Hans - please take a look.
> 
> Resent: Since the namesys.com mail server refuses messages over 40k,
> I've posted the patches at
> ftp://ftp.suse.com/pub/people/jeffm/reiserfs/kernel-v2.6/io-error/
> 
> - -Jeff
> 
> - --
> Jeff Mahoney
> SuSE Labs
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFBRhsvLPWxlyuTD7IRAqa7AJ9ZJa+HnOGYU7OIouWMu34H2mU0MQCgn0H5
> QBdLo95dLiXsQdwojQSHAos=
> =kPTJ
> -----END PGP SIGNATURE-----

-- 
Alex.

  reply	other threads:[~2004-09-15 13:11 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 [this message]
2004-09-15 13:47   ` Jeff Mahoney
2004-09-15 14:12     ` Alex Zarochentsev
2004-09-15 14:30       ` Jeff Mahoney
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=20040915131133.GD5137@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=jeffm@suse.com \
    --cc=reiserfs-list@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.