All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Ryan O'Hara <rohara@redhat.com>
Subject: Re: Fwd: IO error on DM device
Date: Thu, 30 Mar 2006 13:44:45 -0600	[thread overview]
Message-ID: <442C352D.8010604@redhat.com> (raw)
In-Reply-To: <39daa5689df1bf4a05a144891cc3563d@redhat.com>

Jonathan E Brassow wrote:
> 
>     Another observation is that we are not seeing any IO errors when the
>     same test is executed on SLES9 SP3/SP4.
> 

I think Ryan's post is correct, but I wonder why the SLES9 is not 
returning errors. Was the SLES statement referring to the scsi errors 
you see in the log like this:


     Feb  1 11:47:45 apwtest52 kernel: SCSI error : <3 0 0 1> return code
     = 0x20000

or the dm-multipath and block layer messages

Feb  1 11:48:40 apwtest52 kernel: device-mapper: dm-multipath:
     Failing path 8:32.


     Feb  1 11:48:40 apwtest52 kernel: Buffer I/O error on device dm-0,
     logical block 116940 u


or both?

Do you have the same dm-multipath settings (queue if no path, etc)? Is 
this is the qlogic qla2xxx driver? Are there qlogic guys on the list 
that would know if there are any differences between the SLES and RHEL 
drivers or are we going to have to dig in there? Are there differences 
between the SLES and RHEL dm multipath drivers? Does this occur with the 
upstream kernel?

      parent reply	other threads:[~2006-03-30 19:44 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
2006-03-30 19:44 ` Mike Christie [this message]

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=442C352D.8010604@redhat.com \
    --to=mchristi@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=rohara@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.