From: Eric Sandeen <sandeen@sandeen.net>
To: George Barnett <george@alink.co.za>
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruption on ubuntu 2.6.27-9-server
Date: Tue, 03 Feb 2009 20:05:27 -0600 [thread overview]
Message-ID: <4988F7E7.9050008@sandeen.net> (raw)
In-Reply-To: <7B2E904E-498E-4EEC-A09F-4DE823E4FAB0@alink.co.za>
George Barnett wrote:
> On 04/02/2009, at 12:46 PM, Eric Sandeen wrote:
>
>>> bad version number 0x0 on inode 18046
>>> bad magic number 0x0 on inode 18047
>>> bad version number 0x0 on inode 18047
>>> bad directory block magic # 0 in block 0 for directory inode 18000
>> Interesting that all the bad magic numbers were 0... not sure what to
>> make of that, offhand, I'm afraid...
>
> Oh dear.
>
> I'm going to try moving the filesystem to ext3 to see if this
> continues. If it does, it would suggest a bug in the underlying
> raid10 implementation or a problem with the disks, although they're
> not reporting any errors [1].
one thing to note is that xfs is very good at detecting on-disk
corruption, not sure ext3 will be as good. So ext3 may seem to run
finer, longer, even if there is an underlying problem.
> Is there any further debugging I can do before I start fresh?
well, it'd be great to have an isolated testcase, if you can reproduce
it succinctly.
Also I don't know what exact kernel ubuntu uses or what patches are in
it; you might try a stock upstream kernel w/ the same config,
2.6.27.$LATEST, and see if you continue to have problems.
-Eric
> George
>
>
> 1. The hardware ecc recovered smartctl metric is /very/ high,
> although I'm told this may be normal for samsung drives. I cant think
> of any way to confirm a disk problem without a CRC checking fs though.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-04 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 0:32 XFS corruption on ubuntu 2.6.27-9-server George Barnett
2009-02-04 1:28 ` Eric Sandeen
2009-02-04 1:34 ` George Barnett
2009-02-04 1:46 ` Eric Sandeen
2009-02-04 1:53 ` George Barnett
2009-02-04 2:05 ` Eric Sandeen [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=4988F7E7.9050008@sandeen.net \
--to=sandeen@sandeen.net \
--cc=george@alink.co.za \
--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 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.