From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Gabriel Gomiz <gomita@cooperativaobrera.com.ar>,
linux-scsi@vger.kernel.org
Subject: Re: Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem
Date: Fri, 12 May 2006 08:56:52 -0700 [thread overview]
Message-ID: <20060512155652.GA24900@us.ibm.com> (raw)
In-Reply-To: <1147446596.3769.25.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Fri, 2006-05-12 at 11:34 -0300, Gabriel Gomiz wrote:
> > I'm attaching dmesg output. I'm sorry I forgot to attach it in the
> > last
> > email. The I/O errors occur when the devices are being detected and
> > whenever I try to access them. For example to do 'fsidk -l /dev/sdc'.
>
> Well, what I was hoping for was mode sense messages but, unfortunately,
> there aren't any. My suspicion is that the 6285 is dual controller
> running in RDAC mode and you're attached to the inactive controller (in
> that configuration it allowed INQUIRY and MODE SENSE through but errors
> out on all other I/O operations). I think you can verify by physically
> removing one of the controllers and rebooting the array (or just attach
> the SCSI cable to the other controller)
I would agree with your suspicion as the error signature is similar to
ones I receive using some FC based storage in RDAC mode. This problem is
showing up more as we have more storage support move from other multipath
solutions implemented in the mid-layer to using device mapper.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2006-05-12 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 13:29 Symbios-NCR 6285-3621 + Adaptec 2944W multilun problem Gabriel Gomiz
2006-05-12 14:09 ` James Bottomley
2006-05-12 14:34 ` Gabriel Gomiz
2006-05-12 15:09 ` James Bottomley
2006-05-12 15:56 ` Mike Anderson [this message]
2006-05-12 17:19 ` Gabriel Gomiz
2006-05-12 17:22 ` James Bottomley
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=20060512155652.GA24900@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=gomita@cooperativaobrera.com.ar \
--cc=linux-scsi@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