All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Zeimetz <bernd@bzed.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipathing with RHEL4 U2 on EMC DMX
Date: Thu, 16 Feb 2006 22:37:23 +0100	[thread overview]
Message-ID: <43F4F093.4000905@bzed.de> (raw)
In-Reply-To: <2CF4E90F20CF3C4DBD3A71BD9FA2758D122F66@PSCDALPEXCH03.perotsystems.net>

Hi,

>         SCSI error : <0 0 0 6> return code = 0x20000
>         end_request: I/O error, dev sdd, sector 64078960
>         end_request: I/O error, dev sdd, sector 64078961
>         device-mapper: dm-multipath: Failing path 8:48.
>         SCSI error : <1 0 0 6> return code = 0x20000
>         end_request: I/O error, dev sdl, sector 34888112
>         end_request: I/O error, dev sdl, sector 34888113
>         device-mapper: dm-multipath: Failing path 8:176.
>
we had this problem with our buggy CX here, too. I thought that the CX
had some issues, but now I start to think that's a fault on the kernel side.

If anybody is interested - as the buggy CX will be replaced, we're
moving our production data to a different storage until we have the new
machine. The old one will be used as additional disk-to-disk backup, but
I can't see there any problems in testing/debugging stuff with it. At
least I can put it under heavy load and see what will happen.

Any ideas on that?



Best regards,

Bernd Zeimetz
Darmstadt University of Technology

  parent reply	other threads:[~2006-02-16 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10 14:48 Multipathing with RHEL4 U2 on EMC DMX Child, David
2006-02-15 19:52 ` Brian Long
2006-02-16 21:37 ` Bernd Zeimetz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-10 21:39 Child, David
2006-02-13 16:53 Child, David
2006-02-16 21:09 Child, David
2006-02-16 21:45 ` Bernd Zeimetz
2006-02-16 22:05 egoggin

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=43F4F093.4000905@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 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.