From: Simon Kirby <sim@hostway.ca>
To: xfs@oss.sgi.com
Subject: Re: XFS corruption [2.6.30.5+patches.2.6.30.tgz]
Date: Mon, 7 Sep 2009 00:25:34 -0700 [thread overview]
Message-ID: <20090907072534.GC4568@hostway.ca> (raw)
In-Reply-To: <20090907063724.GB4568@hostway.ca>
Hmm, I suspect the corruption here came from the RAID 6 implementation.
I see corruption on another volume on this volume group now. We happened
to test a two drive RAID 6 failure/rebuild shortly before this occurred.
So, perhaps it's not worth looking at this further other than perhaps the
part where the kernel hung. :)
Simon-
On Sun, Sep 06, 2009 at 11:37:24PM -0700, Simon Kirby wrote:
> Hello!
>
> In a backup server attached to a Coraid shelf via AOE and DM, we saw
> 2.6.30.5+patches.2.6.30.tgz die with a corruption problem. The kernel
> logged many similar errors, and then stopped responding some time later.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-09-07 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 6:37 XFS corruption [2.6.30.5+patches.2.6.30.tgz] Simon Kirby
2009-09-07 7:25 ` Simon Kirby [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=20090907072534.GC4568@hostway.ca \
--to=sim@hostway.ca \
--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