From: Nathan Scott <nathans@sgi.com>
To: Callan Tham <callan.tham@securecirt.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: Possible XFS Corruption
Date: Mon, 2 Aug 2004 15:48:54 +1000 [thread overview]
Message-ID: <20040802054854.GD21646@frodo> (raw)
In-Reply-To: <1091420414.7363.17.camel@taz.lan.securecirt.com>
On Mon, Aug 02, 2004 at 12:20:14PM +0800, Callan Tham wrote:
> On Mon, 2004-08-02 at 13:02, Nathan Scott wrote:
> > > I'm running a Gentoo-patched 2.6.7 kernel, and am experiencing possible
> > > XFS corruption on one of my partitions. I've included a sample of the
> >
> > Is it reproducible with an unpatched kernel.org kernel?
> >
> > thanks.
>
> Hi Nathan,
>
> Unfortunately, I am unable to test this with a vanilla kernel. However,
Oh?
> looking through the Gentoo patches, they did not touch any of the XFS
> code in a vanilla 2.6.7 kernel.
I would be surprised if they had. A more likely source of
problems would be changes in the VM subsystem (XFS metadata
buffers are cached in the page cache).
> Is there any other way to diagnose this?
The failure you see is XFS reporting corruption in a directory
btree buffer which didn't have an appropriate magic number at
its start when read in from disk. There's thousands of potential
reasons why that may have happened; more often than not these
days its an error thats occured outside of XFS though, and XFS
is passing on the bad news.
If you can find a reproducible test case, you're half way there.
If you can find a reproducible test case on a kernel.org kernel,
you're 95% of the way there, cos then we can more easily help. ;)
cheers.
--
Nathan
next prev parent reply other threads:[~2004-08-02 4:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 3:49 Possible XFS Corruption Callan Tham
2004-08-02 5:02 ` Nathan Scott
2004-08-02 4:20 ` Callan Tham
2004-08-02 5:48 ` Nathan Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-07 11:49 possible xfs corruption blacknred
2010-12-07 14:10 ` Emmanuel Florac
2010-12-07 15:11 ` blacknred
2010-12-07 15:42 ` Emmanuel Florac
2010-12-07 17:30 ` blacknred
2010-12-07 18:15 ` Stan Hoeppner
2010-12-07 19:32 ` Michael Monnerie
2010-12-07 22:10 ` Dave Chinner
2010-12-09 3:44 ` Eric Sandeen
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=20040802054854.GD21646@frodo \
--to=nathans@sgi.com \
--cc=callan.tham@securecirt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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 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.