From: Markus Schoder <lists@gammarayburst.de>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_RETURN
Date: Fri, 24 Aug 2007 20:19:04 +0100 [thread overview]
Message-ID: <200708242019.04219.lists@gammarayburst.de> (raw)
In-Reply-To: <20070824014313.GE72985246@sgi.com>
On Friday 24 August 2007, David Chinner wrote:
> On Thu, Aug 23, 2007 at 09:09:50PM +0100, Markus Schoder wrote:
> > Got a bunch of the below errors in the log. It occured during a
> > Debian upgrade with aptitude. xfs_repair found a lost inode.
>
> Can you post the output of xfs_repair if you still have it? It
> would be handy to correlæte the shutdown to an actual error on
> disk....
Unfortunately I don't have the output anymore. From memory I recall
there were two messsages indicating problems:
1. A message about rebuilding a directory at inode 128.
2. A lost inode that was moved to lost+found.
Other than that there were only the usual progress messages.
> > Kernel is stock 2.6.22.4 plus CFS patch. This is a 64bit kernel on
> > an amd64 processor.
>
> Hmmmm - so not exactly a stock kernel then. Which of the 19 versions
> the CFS patch was applied? Is it reproducable or only a one-off?
> if it's not a one-off problem, have you seen the problem without the
> CFS patch?
It is version 19.1 and the problem was a one-off never seen it before or
since.
--
Markus
next prev parent reply other threads:[~2007-08-24 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 20:09 XFS internal error XFS_WANT_CORRUPTED_RETURN Markus Schoder
2007-08-24 1:43 ` David Chinner
2007-08-24 19:19 ` Markus Schoder [this message]
2007-08-24 2:02 ` Timothy Shimmin
2007-08-24 19:23 ` Markus Schoder
-- strict thread matches above, loose matches on Subject: below --
2013-12-11 17:27 XFS: Internal " Dave Jones
2013-12-11 18:52 ` Chris Murphy
2013-12-11 18:57 ` Dave Jones
2013-12-12 0:19 ` Chris Murphy
2013-12-13 9:46 ` Stan Hoeppner
2013-12-11 23:01 ` Dave Chinner
2013-12-12 16:14 ` Eric Sandeen
2013-12-12 16:20 ` Dave Jones
2013-12-12 21:27 ` Dave Chinner
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=200708242019.04219.lists@gammarayburst.de \
--to=lists@gammarayburst.de \
--cc=dgc@sgi.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox