From: Bernd Zeimetz <bernd@bzed.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Fwd: IO error on DM device
Date: Fri, 31 Mar 2006 00:48:56 +0200 [thread overview]
Message-ID: <442C6058.2060006@bzed.de> (raw)
In-Reply-To: <442C2AAC.1020405@redhat.com>
Hi,
> So based on the comments below and steps to reproduce, I'd say this is
> expected behavior since multipathd is turned off. What happens if
> multipathd is left running? It is implied that not stopping multipathd
> will still cause a failure but will take much longer. I am no expert
> on multipathd, so perhaps one of the dm developers can comment on
> multipathd handling these SCSI error.
Unfortunately I've seen these errors occuring with an EMC CX attached to
a single host, which was running multipath, too. It happened very, very
rarely and just completely random. I didn't find any way to make it
reproducible.
Best regards,
Bernd
next prev parent reply other threads:[~2006-03-30 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39daa5689df1bf4a05a144891cc3563d@redhat.com>
2006-03-30 18:59 ` Fwd: IO error on DM device Ryan O'Hara
2006-03-30 22:48 ` Bernd Zeimetz [this message]
2006-03-30 19:44 ` Mike Christie
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=442C6058.2060006@bzed.de \
--to=bernd@bzed.de \
--cc=dm-devel@redhat.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