All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipath failover issues
Date: Mon, 16 Mar 2009 10:59:17 -0700	[thread overview]
Message-ID: <1237226357.309.6.camel@chandra-ubuntu> (raw)
In-Reply-To: <49BE7C9C.8020100@directi.com>


On Mon, 2009-03-16 at 21:51 +0530, dushyanth.h@directi.com wrote:
> Hi guys,
> 
> Iam using dm-multipath for a Infortrend dual controller F16F-R4031-6 FC
> system.
> 
> Version details are :
> 
> device-mapper-multipath-0.4.7-17.el5
> device-mapper-1.02.24-1.el5
> device-mapper-event-1.02.24-1.el5
> 
> OS : Red Hat Enterprise Linux Server release 5.2 (Tikanga)
> Kernel : 2.6.18-92.1.10.el5 #1 SMP x86_64 x86_64 x86_64
> 
> Recently, one of the RAID controllers failed and caused multipath to
> fail both active paths
> 
> device-mapper: multipath: Failing path 8:32.

8:32 has failed here.
> sd 2:0:0:0: SCSI error: return code = 0x00020000

error code 20000 mean the BUS is busy.

> end_request: I/O error, dev sdd, sector 1976776672
> device-mapper: multipath: Failing path 8:48.

and 8:48 failed because of that.

Do you know which one was supposed to fail when the RAID controller
failed ? (my guess is it is 8:32).

looks like for whatever reason the other SCSI bus became busy.
> sd 2:0:0:0: SCSI error: return code = 0x00020000
> end_request: I/O error, dev sdd, sector 1967432880
> sd 2:0:0:0: SCSI error: return code = 0x00020000
> end_request: I/O error, dev sdd, sector 161647296
> 
> This caused the ext3 filesystem to go into a read only mode. Full IO
> errors is at http://pastebin.com/m103325d9
> 
> The dual controller storage unit and the host server (Only 1 Server
> using 2 Qlogic FC HBAs) are hooked upto two different Qlogic SanBox FC
> switch for redundancy.
> 
> multipath.conf : http://pastebin.com/m4c7da817
> multipath -v4 -ll : http://pastebin.com/m7d863925
> 
> I have checked the logs on the FC switch and the HBAs
> and i dont see any event which suggest both paths failed at once. Even
> the errors i captured out of dmesg show that one of the physical disks
> that makes up dm-0 had 'end_request: I/O errors' while the other did not
> have any such error.
> 
> sd 2:0:0:0: SCSI error: return code = 0x00020000
> end_request: I/O error, dev sdd, sector 1967432880
> sd 2:0:0:0: SCSI error: return code = 0x00020000
> end_request: I/O error, dev sdd, sector 161647296
> 
> At this point iam wondering how paths 8:32 and 8:48 failed together -
> considering both paths are through two different FC switches. Any
> suggestions on this ?
> 
> Additionaly, I have looked at the mailing list archives & annotated conf
> files and found two options a) failback and b) no_path_retry. What would
> be the best recommended values for these on a dual controller setup like
> mine ?
> 
> It would also be helpful if someone could share infotrend specific
> settings multipath settings.
> 
> TIA
> Dushyanth
> 
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

  parent reply	other threads:[~2009-03-16 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 16:21 Multipath failover issues dushyanth.h
2009-03-16 16:49 ` Bryn M. Reeves
2009-03-16 16:50 ` Bryn M. Reeves
2009-03-16 17:59 ` Chandra Seetharaman [this message]
2009-03-16 21:03   ` dushyanth.h
2009-03-16 22:40     ` Chandra Seetharaman
2009-03-17 12:30       ` Dushyanth Harinath

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=1237226357.309.6.camel@chandra-ubuntu \
    --to=sekharan@us.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=sekharan@linux.vnet.ibm.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.