From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair breaks with assertion
Date: Thu, 11 Apr 2013 04:55:53 -0500 [thread overview]
Message-ID: <516688A9.8050506@hardwarefreak.com> (raw)
In-Reply-To: <CAPaMSRCq0f+GqTbRRCXBFUDdtmpBx=VjBaOLpdDytXunL9dfmQ@mail.gmail.com>
On 4/11/2013 1:34 AM, Victor K wrote:
> The raid array did not suffer, at least, not according to mdadm; it is now
> happily recovering the one disk that officially failed, but the whole thing
> assembled without a problem
> There was a similar crash several weeks ago on this same array, but had
> ext4 system back then.
> I was able to save some of the latest stuff, and decided to move to xfs as
> something more reliable.
> I suspect now I should also had replaced the disk controller then.
Rebuilds are *supposed* to be transparent to the filesystem but this is
not always the case. Sometimes due to bugs. In fact we just recently
saw an LVM bug wherein a pvmove operation was not transparent, and hosed
up an XFS. This is but one of many reasons I prefer hardware based RAID
and volume management. It isolates these functions and RAID memory
structures from the kernel, and thus prevents such bugs from causing
problems. This may/not be the source of your apparent XFS corruption.
We don't have enough (log) data to ascertain the cause at this point.
Running repair on an 8/10TB filesystem while md is rebuilding the
underlying RAID6 array isn't something I'd put a lot of trust in. Wait
until the rebuild is finished and then run a non-destructive repair.
Compare the results to the previous repair.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-04-11 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 5:25 xfs_repair breaks with assertion Victor K
2013-04-11 6:25 ` Dave Chinner
2013-04-11 6:34 ` Victor K
2013-04-11 7:02 ` Dave Chinner
2013-04-11 9:55 ` Stan Hoeppner [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=516688A9.8050506@hardwarefreak.com \
--to=stan@hardwarefreak.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 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.