From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm and duplicates...
Date: Thu, 8 Jun 2006 07:52:33 +0200 [thread overview]
Message-ID: <20060608055232.GD18061@percy.comedia.it> (raw)
In-Reply-To: <5485940d0606071038h7c823b7do58e95a486618d643@mail.gmail.com>
On Wed, Jun 07, 2006 at 06:38:49PM +0100, C'est Pierre wrote:
>Greetings,
>
>I'm trying to setup a cluster with ServiceGuard but I am going through
>a lot of hassles doing so. I did a mistake initially by trying to
>pvcreate the 2 luns of the same physical disk from our storage (fiber
>channel) and now, while trying to create a new logical volume, I get
>this weird error, for the record the sda and sdb are the 2 luns coming
>from different paths (cards):
>
you posted before about multipathing,
and you got one answer.
what did you do for the multipathing issue you had?
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2006-06-08 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 17:38 [linux-lvm] lvm and duplicates C'est Pierre
2006-06-08 5:52 ` Luca Berra [this message]
2006-06-08 9:48 ` C'est Pierre
2006-06-08 19:52 ` Luca Berra
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=20060608055232.GD18061@percy.comedia.it \
--to=bluca@comedia.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox