All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonello Piemonte <apiemont@eso.org>
To: dm-devel@redhat.com
Subject: raw devices with multipathing and SUN Storedge 3511
Date: Tue, 8 Aug 2006 11:00:50 +0200	[thread overview]
Message-ID: <200608081100.50317.apiemont@eso.org> (raw)

Hello

I have two questions:

1) is it ok to use raw devices with device mapper and multipathing?

I have the following simple setup under RHEL4.3 (x86_64), e.g. one LUN
exported from a SUNStoredge 3511 directly to the host which has two HBA,
therefore I see the same LUN twice, as sdc and sdd:

# multipath -l
mpath2 (3600c0ff00000000009279811b3f44a00)
[size=1862 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [active]
 \_ 1:0:0:0     sdc 8:32  [active][ready]
 \_ 2:0:0:0     sdd 8:48  [active][ready]

I made 2 partitions on the mpath2 device and used kpartx to make is 
visible to device mapper, e.g.

# ll /dev/mpath/
total 0
lrwxrwxrwx  1 root root 7 Aug  7 17:50 mpath2 -> ../dm-0
lrwxrwxrwx  1 root root 7 Aug  8 10:32 mpath2p1 -> ../dm-1
lrwxrwxrwx  1 root root 7 Aug  8 10:32 mpath2p2 -> ../dm-2

if I then proceed to asssigne raw devices, it seems to work
# raw /dev/raw/raw2 /dev/dm-2
/dev/raw/raw2:  bound to major 253, minor 2
# raw -qa
/dev/raw/raw2:  bound to major 253, minor 2

is then suitable to use /dev/raw/raw2 with databases
(namely sybase ASE 15)?

2) second question: is the SUN Storedge 3511 an active/active array and if 
not, do I need to worry about hardware handlers specific for it?

many thanks for your help!
antonello

                 reply	other threads:[~2006-08-08  9:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200608081100.50317.apiemont@eso.org \
    --to=apiemont@eso.org \
    --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.