From: Nathan Scott <nathans@sgi.com>
To: Marek Materzok <tilk@lucifer.czad.org>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: XFS oops, kernel 2.4.30 w/grsecurity
Date: Fri, 10 Jun 2005 11:52:41 +1000 [thread overview]
Message-ID: <20050610015241.GF791@frodo> (raw)
In-Reply-To: <1118062022.6266.19.camel@lucifer.czad.org>
On Mon, Jun 06, 2005 at 02:47:02PM +0200, Marek Materzok wrote:
> Jun 6 11:40:08 lucifer kernel: Filesystem "ide0(3,6)": XFS internal error xfs_btree_check_lblock at line 222 of file xfs_btree.c. Caller 0xc01ed58d
> Jun 6 11:40:08 lucifer kernel: c9871750 c01efc41 c0374857 00000001 d71ffc00 c037484b 000000de c01ed58d
> Jun 6 11:40:08 lucifer kernel: c8bd4f80 d76b2940 00ca1740 00000000 00000008 00000000 c987178c cf416124
> ...
> Then, the /home partition (/dev/hda6) was disabled, and every access to
> it ended with EIO. A reboot fixed the problem - the filesystem was
> rebuilt and mounted correctly. Nothing like this happened ever to my XFS
> filesystems.
This isn't an oops, its what XFS does when it detects on-disk
metadata corruption - it shuts down the filesystem, reports a
kernel stack trace and some other diagnostics, and returns EIO
on subsequent accesses to the filesystem until the problem is
resolved and the filesystem is mounted once more.
cheers.
--
Nathan
prev parent reply other threads:[~2005-06-10 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 12:47 XFS oops, kernel 2.4.30 w/grsecurity Marek Materzok
2005-06-10 1:52 ` Nathan Scott [this message]
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=20050610015241.GF791@frodo \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=tilk@lucifer.czad.org \
/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.