All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arshavir Grigorian <ag@m-cam.com>
To: henrik@morsing.cc,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvcreate issues
Date: Wed, 01 Jun 2005 13:59:30 -0400	[thread overview]
Message-ID: <429DF782.2070209@m-cam.com> (raw)
In-Reply-To: <42296.195.190.132.207.1117172724.squirrel@webmail.morsing.org>

Henrik Morsing wrote:
>>AJ Lewis wrote:
>>
>>>On Mon, May 23, 2005 at 02:48:11PM -0400, Arshavir Grigorian wrote:
>>>
>>>
>>>You're sure sd[c-f] is not the same device on multiple paths?
>>>
>>
>>How can I be sure? How do I check?
>>
>>This SAN exports another set of 4 LUNs to a different server and they
>>work just fine.
> 
> 
> It does look like you're seing the same disk through four different paths.
> What OS is the other server running? The people that setup the SAN should
> know if it is multi pathed or not.
> 

Thanks.

Looks like it might be a problem with the type of firmware we have on 
the SAN which only allows for one active fiber channel controller at a 
time. The second controller should be used only when the first one 
fails. What we were doing was to export the first set of 4 volumes 
through one controller and another set of 4 on the other controller, 
hence the problem. We will either have to change the firmware to allow 
for 2 active controllers (no failover spare) or buy a switch to make all 
the volumes accessible to more than one server through the first fc 
controller.

-- 
Arshavir Grigorian
Systems Administrator/Engineer

      reply	other threads:[~2005-06-01 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 18:48 [linux-lvm] pvcreate issues Arshavir Grigorian
2005-05-23 20:03 ` AJ Lewis
2005-05-26 14:27   ` Arshavir Grigorian
2005-05-27  5:45     ` Henrik Morsing
2005-06-01 17:59       ` Arshavir Grigorian [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=429DF782.2070209@m-cam.com \
    --to=ag@m-cam.com \
    --cc=henrik@morsing.cc \
    --cc=linux-lvm@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.