From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] reiserfs panic
Date: Fri Nov 30 07:55:03 2001 [thread overview]
Message-ID: <742840000.1007128632@tiny> (raw)
In-Reply-To: <20011130102423.E1452@tykepenguin.com>
On Friday, November 30, 2001 10:24:23 AM +0000 Patrick Caulfield
<patrick@tykepenguin.com> wrote:
> I'm posting this here partly because I hope Chris Mason is reading(!) and
> partly because it may be of some use to others on the list.
;-)
>
> There seems to be a problem when reading from a deactivated snapshot of a
> reiserfs volume that causes a panic.
>
> The problem is caused by the fact that when a snapshot becomes full, LVM
> returns I/O errors for the volume and when reiserfs hits an I/O error it
> panics.
>
> The solution is, of course, to make your snapshots large enough that this
> never happens :-) but just in case this is not possible the following patch
> may be of use:
>
>
> diff -u fs/reiserfs/namei.c.orig fs/reiserfs/namei.c
> --- fs/reiserfs/namei.c.orig Thu Nov 29 16:13:28 2001
> +++ fs/reiserfs/namei.c Thu Nov 29 16:34:49 2001
> @@ -320,9 +320,10 @@
>
> while (1) {
> retval = search_by_entry_key (dir->i_sb, &key_to_search,
> path_to_entry, de); - if (retval == IO_ERROR)
> + if (retval == IO_ERROR)
> + return NAME_NOT_FOUND;
The problem here is that NAME_NOT_FOUND does not mean error. It means it is
safe to insert something with that name, which isn't what we want. For
snapshots though, it will work fine.
Now that 2.5.x is out I expect more of these to get cleaned up, and I'm
workin on patches to turn reiserfs_panic into a forced readonly mount.
-chris
next prev parent reply other threads:[~2001-11-30 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011129164915.I1408@tykepenguin.com>
2001-11-30 4:22 ` [linux-lvm] reiserfs panic Patrick Caulfield
2001-11-30 7:55 ` Chris Mason [this message]
2001-11-30 8:04 ` Patrick Caulfield
2001-11-30 10:31 ` Andreas Dilger
2001-12-29 22:31 ` [linux-lvm] Fun little horror story -- please add to FAQ if it isn't already documented Chris Worley
2001-12-30 5:05 ` Ben Holness
2001-12-30 9:29 ` Steven Lembark
2001-11-30 17:59 ` [linux-lvm] reiserfs panic Ed Tomlinson
2001-11-30 18:51 ` Andreas Dilger
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=742840000.1007128632@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.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.