From: Tom Maddox <tmaddox@thereinc.com>
To: Kanoa Withington <kanoa@cfht.hawaii.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Bizarre RAID "failure"
Date: Thu, 19 Feb 2004 16:44:42 -0800 [thread overview]
Message-ID: <1077237882.9970.4.camel@s8n-1.thereinc.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0402191434590.6370@umi.cfht.hawaii.edu>
On Thu, 2004-02-19 at 16:39, Kanoa Withington wrote:
> It might not be related but I've seen odd behaviour with that kernel
> and XFS family when xfs_repair/XFS Recovery is run while the array is
> resyncing.
>
> If you have the opportunity to try some tests, you might try booting
> the system without the volume mounted to avoid the automatic XFS
> checking. When the resync is complete, then try mounting the volume.
>
> -Kanoa
Yep, tried that. I got identical results, unfortunately.
Thanks,
Tom
next prev parent reply other threads:[~2004-02-20 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 22:44 Bizarre RAID "failure" Tom Maddox
2004-02-19 23:38 ` Måns Rullgård
2004-02-20 0:39 ` Kanoa Withington
2004-02-20 0:44 ` Tom Maddox [this message]
2004-02-20 8:33 ` Nathan Hunsperger
2004-03-02 16:56 ` Corey McGuire
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=1077237882.9970.4.camel@s8n-1.thereinc.com \
--to=tmaddox@thereinc.com \
--cc=kanoa@cfht.hawaii.edu \
--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).