linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rainer Duffner <rainer@ultra-secure.de>
To: C'est Pierre <cestpierre@gmail.com>
Cc: linux-scsi@vger.kernel.org, suse-sles-e@suse.com
Subject: Re: fdisk weirdness.
Date: Thu, 25 May 2006 00:50:13 +0200	[thread overview]
Message-ID: <4474E325.60809@ultra-secure.de> (raw)
In-Reply-To: <5485940d0605241356j1128e38aq1049a9686265547f@mail.gmail.com>

C'est Pierre wrote:
> Greetings,
>
> I've been trying to setup a server for a cluster that is attached to a
> fibre channel storage (an HP EVA 3000 hsv100). Prior to allocating a
> vdisk on the storage for this server, whenever I'd issue "fdisk -l",
> it wouldn't print anything at all. After correctly alocating the disk
> on the Storage, it shown 2 disks, sda and sdb. At this point, I assume
> they're 2 LUNS for the same vdisk, being that the Storage attached
> through two different FC cards for redundancy/failover - feel free to
> correct me if I am wrong. However, the /dev/cciss/c0d0[pN] (compaq
> smartarray or something) doesn't show up on it's output.
>
> Any hints?
>
> Thank you,
> Pierre
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
> For additional commands, e-mail: suse-sles-e-help@suse.com
>




You will probably want to install one of HPs failover-capable drivers:
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=315741&locale=en_US&taskId=135&prodSeriesId=315739&prodTypeId=12169&swEnvOID=2026


This is for 2 GBit/s Qlogic-HBA, more or less regardless of the OEM.
(worked for IBM, too, for us).




cheers,
Rainer

      reply	other threads:[~2006-05-24 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24 20:56 fdisk weirdness C'est Pierre
2006-05-24 22:50 ` Rainer Duffner [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=4474E325.60809@ultra-secure.de \
    --to=rainer@ultra-secure.de \
    --cc=cestpierre@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=suse-sles-e@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).