All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: NIC and HBA based multipathing
Date: Tue, 6 Nov 2007 15:01:57 -0800	[thread overview]
Message-ID: <20071106230157.GA23800@linux.vnet.ibm.com> (raw)
In-Reply-To: <342d47870711061433h6dce42baj705aca5ae7baa466@mail.gmail.com>

Scott Moseman <scmoseman@gmail.com> wrote:
> On Nov 6, 2007 4:20 PM, Mike Anderson <andmike@linux.vnet.ibm.com> wrote:
> >
> > > # mount /dev/sdb1 /sanHBA
> > > mount: /dev/sdb1 already mounted or /sanHBA busy
> >
> > It appears something else has claimed the device prior to your mount call.
> >         - Is it lvm? Run pvs and see if the device was claimed. If that is
> >           not what you want you may need to use the lvm.conf filters.
> >
> 
> Here's what's in dmesg...
> 
> scsi1 : qla4xxx
>  QLogic iSCSI HBA Driver version: 5.01.00.08
>   QLogic ISP4032 @ 0000:14:01.1 hdma+, host#=1, fw=03.00.01.24
>   Vendor: EQLOGIC   Model: 100E-00           Rev: 2.3
>   Type:   Direct-Access                      ANSI SCSI revision: 05
> qla4xxx 0000:14:01.1: scsi(1:0:1:0): Enabled tagged queuing, queue depth 32.
> SCSI device sdb: 8417280 512-byte hdwr sectors (4310 MB)
> SCSI device sdb: drive cache: write through
>  sdb: sdb1
> Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
> 
> I can fdisk the /dev/sdb drive and it's the SAN partition alright.

Are there any dm messages in the dmesg output? 

Are you sure dm multipath did not grab the device(s) on boot?

What is the output of multipath -l?

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com

  parent reply	other threads:[~2007-11-06 23:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 16:56 NIC and HBA based multipathing Scott Moseman
2007-10-30 17:40 ` Kevin Foote
2007-10-30 19:11   ` Scott Moseman
2007-11-01 19:53     ` Mike Christie
2007-11-01 20:21       ` Scott Moseman
2007-11-01 21:57         ` Mike Anderson
2007-11-01 22:09           ` Mike Anderson
2007-11-06 21:08           ` Scott Moseman
2007-11-06 22:20             ` Mike Anderson
2007-11-06 22:33               ` Scott Moseman
2007-11-06 22:54                 ` malahal
2007-11-06 23:51                   ` Upgrade issues with v4.8 Paul Cote
2007-11-06 23:01                 ` Mike Anderson [this message]
2007-11-07  1:46                   ` NIC and HBA based multipathing Scott Moseman
2007-11-07  2:59                     ` malahal
2007-11-07  5:09                       ` Mike Anderson
2007-11-07 15:07                         ` Scott Moseman
2007-11-12 17:54                           ` Scott Moseman
2007-11-12 20:18                             ` Mike Anderson
2007-11-12 20:34                               ` Scott Moseman
2007-11-13 16:52                                 ` Scott Moseman
2007-11-15 18:00                                   ` Scott Moseman
2007-11-15 18:31                                     ` checker msg is "emc_clariion_checker: Path not correctly configured for failover" Paul Cote
2007-11-15 18:44                                     ` NIC and HBA based multipathing Mike Christie
2007-11-15 19:16                                       ` Mike Anderson
2007-11-15 20:26                                         ` Scott Moseman
2007-11-15 20:40                                           ` Scott Moseman

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=20071106230157.GA23800@linux.vnet.ibm.com \
    --to=andmike@linux.vnet.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.