From: Andreas Dilger <adilger@turbolabs.com>
To: Chris Mason <mason@suse.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] reiserfs panic
Date: Fri Nov 30 10:31:02 2001 [thread overview]
Message-ID: <20011130093239.E15936@lynx.no> (raw)
In-Reply-To: <742840000.1007128632@tiny>; from mason@suse.com on Fri, Nov 30, 2001 at 08:57:12AM -0500
On Nov 30, 2001 08:57 -0500, Chris Mason wrote:
> 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.
Just as an FYI, ext2 has a distinction between "ext2_panic", "ext2_error",
and "ext2_warning". The panic is just what it sounds like (and can only
be triggered by something like memory corruption, it is almost unused).
The error has a configurable behaviour - panic also, ro-mount, warning.
In all cases, it marks the filesystem superblock with an error. The
default is ro-mounting the filesystem. The warning is just a warning
(unusual condition, but a 100% recoverable situation).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-30 10:31 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
2001-11-30 8:04 ` Patrick Caulfield
2001-11-30 10:31 ` Andreas Dilger [this message]
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=20011130093239.E15936@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.com \
--cc=mason@suse.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.