From: "Lars Täuber" <taeuber@bbaw.de>
To: Gabor Gombas <gombasg@sztaki.hu>
Cc: linux-raid@vger.kernel.org, sah@coraid.com, ecashin@coraid.com
Subject: Re: RAID1 over aoe devices freezes cp-procs on failure of one aoe device
Date: Fri, 6 Jun 2008 12:03:40 +0200 [thread overview]
Message-ID: <20080606120340.b2e7d25b.taeuber@bbaw.de> (raw)
In-Reply-To: <20080606073416.GC10273@boogie.lpds.sztaki.hu>
Hallo Gabor,
Gabor Gombas <gombasg@sztaki.hu> schrieb:
> On Thu, Jun 05, 2008 at 04:25:02PM +0200, Lars Täuber wrote:
>
> > The lost aoe-device is correctly marked as faulty but the the raid is
> > not usable for a copying processes any more although the remaining
> > device should be enough for a RAID1. There was no change after
> > removing the faulty device from md9.
> >
> > Is it possible that one faulty aoe-device blocks the aoe-module anyhow
> > so that all other aoe devices aren't accessible anymore? Or is the
> > RAID subsystem responsible for this?
>
> It should be easy to test: when the RAID hangs, try to read directly
> from the remaining device ("dd if=/dev/etherd/e11.1 ..."). If that also
> hangs, then it is an AoE issue.
the easiest tests are the last that come to mind. :o)
There is another problem here:
The described problem is not reproducable. I'm not sure wether I made something wrong or the situation is not the same after the shutdown.
I'm checking this right now.
Thanks
Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-06 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 14:25 RAID1 over aoe devices freezes cp-procs on failure of one aoe device Lars Täuber
2008-06-06 7:34 ` Gabor Gombas
2008-06-06 10:03 ` Lars Täuber [this message]
2008-06-09 17:32 ` Ed L. Cashin
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=20080606120340.b2e7d25b.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--cc=ecashin@coraid.com \
--cc=gombasg@sztaki.hu \
--cc=linux-raid@vger.kernel.org \
--cc=sah@coraid.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;
as well as URLs for NNTP newsgroup(s).