From: David Greaves <david@dgreaves.com>
To: Chris Eddington <chrise@synplicity.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 assemble after dual sata port failure
Date: Sun, 11 Nov 2007 17:09:26 +0000 [thread overview]
Message-ID: <47373746.9090701@dgreaves.com> (raw)
In-Reply-To: <4735FC7E.7030601@synplicity.com>
Chris Eddington wrote:
> Hi,
>
> Thanks for the pointer on xfs_repair -n , it actually tells me something
> (some listed below) but I'm not sure what it means but there seems to be
> a lot of data loss. One complication is I see an error message in ata6,
> so I moved the disks around thinking it was a flaky sata port, but I see
> the error again on ata4 so it seems to follow the disk. But it happens
> exactly at the same time during xfs_repair sequence, so I don't think it
> is a flaky disk.
Does dmesg have any info/sata errors?
xfs_repair will have problems if the disk is bad. You may want to image the disk
(possibly onto the 'spare'?) if it is bad.
> I'll go to the xfs mailing list on this.
Very good idea :)
> Is there a way to be sure the disk order is right?
The order looks right to me.
xfs_repair wouldn't recognise it as well as it does if the order was wrong.
> not way out of wack since I'm seeing so much from xfs_repair. Also
> since I've been moving the disks around, I want to be sure I have the
> right order.
Bear in mind that -n stops the repair fixing a problem. Then as the 'repair'
proceeds it becomes very confused by problems that should have been fixed.
This is evident in the superblock issue (which also probably explains the failed
mount).
>
> Is there a way to try restoring using the other disk?
No the event count was very out of date.
next prev parent reply other threads:[~2007-11-11 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 20:28 Raid5 assemble after dual sata port failure Chris Eddington
2007-11-08 10:33 ` David Greaves
2007-11-09 21:23 ` Chris Eddington
2007-11-10 0:28 ` Chris Eddington
2007-11-10 9:16 ` David Greaves
2007-11-10 18:46 ` Chris Eddington
2007-11-11 17:09 ` David Greaves [this message]
2007-11-11 17:41 ` Chris Eddington
2007-11-11 22:49 ` David Greaves
2007-11-12 1:01 ` Bill Davidsen
2007-11-17 6:31 ` Chris Eddington
2007-11-18 12:25 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 20:23 chrise
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=47373746.9090701@dgreaves.com \
--to=david@dgreaves.com \
--cc=chrise@synplicity.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).