All of lore.kernel.org
 help / color / mirror / Atom feed
From: malahal@us.ibm.com
To: dm-devel@redhat.com
Subject: Re: RE: Problem with multipathd and a blacklisted device
Date: Tue, 24 Mar 2009 06:42:09 -0700	[thread overview]
Message-ID: <20090324134209.GA12464@us.ibm.com> (raw)
In-Reply-To: <5635940A0F6F36478CF4D01273B16CA32B9CE52C1E@GVW1096EXB.americas.hpqcorp.net>

Ransegnola, Lori [Lori.Ransegnola@hp.com] wrote:
> I sent this question last week and have not heard a thing.  Do you have a suggestion of a better mailing list that I should use for this question?
> 
> Thank you.
> 
> Lori
> 
> > -----Original Message-----
> > From: Ransegnola, Lori
> > Sent: Thursday, March 19, 2009 3:51 PM
> > To: dm-devel@redhat.com
> > Cc: Ransegnola, Lori
> > Subject: Problem with multipathd and a blacklisted device
> >
> > Configuration:
> > --------------
> >
> > I have a multipath configuration set up where 10 disks are
> > multipathed and 2 disks are blacklisted and are not
> > multipathed.  Here are the relevant parts of the multipath.conf file:
> >
> > defaults {
> >         udev_dir                /dev
> >         polling_interval        10
> >         selector                "round-robin 0"
> > #       path_grouping_policy    multibus
> >         getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
> >         prio_callout            /bin/true
> > #       path_checker            readsector0
> >         path_checker            tur
> >         rr_min_io               100
> >         rr_weight               priorities
> >         failback                immediate
> >         no_path_retry           fail
> >         user_friendly_name      yes
> > }
> >
> > blacklist {
> > #       wwid 26353900f02796769
> > #       devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
> > #       devnode "^hd[a-z]"
> >         wwid                    35000c5000a41f72b
> >         wwid                    35000c5000a41f98b
> >         devnode "^cciss!c[0-9]d[0-9]*"
> > }
> >
> >
> > The two disks that are not multipathed have udev rules and
> > are part of a software RAID set.  The devices show up as
> >
> > /etc/udev/rules.d> ls -l /dev/hpdev
> > total 0
> > lrwxrwxrwx 1 root root 7 Mar 18 10:50 sda1 -> ../sda1
> > lrwxrwxrwx 1 root root 7 Mar 18 03:32 sdb1 -> ../sdb1
> >
> > /dev/md0 is created with sda and sdb.  Here is the bottom of
> > the 'mdadm --detail /dev/md0' output:
> >
> > /root> mdadm --detail /dev/md0
> > /dev/md0:
> >         Version
> > ...
> > Failed Devices : 0
> >   Spare Devices : 0
> >
> >            UUID : 94813396:a3e341fc:c5d4b8ba:0617a019
> >          Events : 0.84
> >
> >     Number   Major   Minor   RaidDevice State
> >        0       8        1        0      active sync   /dev/sda1
> >        1       8       17        1      active sync   /dev/sdb1
> > /root>
> >
> > I am running on a Linux RHEL5 U2 system.
> > /etc/udev/rules.d> uname -a
> > Linux n0 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007
> > x86_64 x86_64 x86_64 GNU/Linux /etc/udev/rules.d> multipath
> > -v Missing option arguement multipath-tools v0.4.7 (03/12, 2006)
> > ----------------------------
> >
> > Problem:
> >
> > This configuration works well until I do some failure testing
> > with one of the 2 blacklisted devs in the software RAID set.
> > I found that if I temporarily remove disk sda and put it back
> > a minute later the disk path, /dev/hpdev/sda1, is removed, even
> > though it is blacklisted.

What is 'multipath -ll' output before you remove the blacklisted device?
What is 'multipath -ll' output after you put the device back a minute
later?

Thanks, Malahal.

  reply	other threads:[~2009-03-24 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5635940A0F6F36478CF4D01273B16CA32B9C3EDDF8@GVW1096EXB.americas.hpqcorp.net>
2009-03-24 13:27 ` Problem with multipathd and a blacklisted device Ransegnola, Lori
2009-03-24 13:42   ` malahal [this message]
2009-03-24 21:12     ` Ransegnola, Lori
2009-03-31 15:27       ` Ransegnola, Lori
2009-03-31 15:49   ` Benjamin Marzinski
2009-04-01 13:40     ` Ransegnola, Lori

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=20090324134209.GA12464@us.ibm.com \
    --to=malahal@us.ibm.com \
    --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.