From: Christophe Varoqui <christophe.varoqui@free.fr>
To: shahid.shaikh@patni.com, device-mapper development <dm-devel@redhat.com>
Subject: Re: LVM Multipathing
Date: Sun, 13 Feb 2005 12:53:00 +0100 [thread overview]
Message-ID: <420F3F9C.3050809@free.fr> (raw)
In-Reply-To: <000101c511bf$41a22be0$11051aac@pcp41116>
I was thinking about that part :
---
3. LVM2 doesn't see my multipathed devices as PV, what's up ?
By default, lvm2 does not consider device-mapper block devices (such as
a dm-crypt device) for use as physical volumes.
In order to use a dm-crypt device as an lvm2 pv, add this line to the
devices block in /etc/lvm/lvm.conf:
types = [ "device-mapper", 16 ]
If /etc/lvm/lvm.conf does not exist, you can create one based on your
current/default config like so:
lvm dumpconfig > /etc/lvm/lvm.conf
(tip from Christophe Saout)
---
... then again,
"you need to exclude the paths from the scaning"
regards,
cvaroqui
shahid shaikh wrote:
>Hello,
>
>I seen FAQ. Part relevant to me from FAQ (copied below) consist semething
>related to files /etc/mkinitrd/modules and
>/etc/mkinitrd/scripts.
>But these files are not peresnt at the given location on my system.
>I have installed udev-021-36.32 and multipath-tools-0.2.1 ( one which come
>bundled with SLES9).
>Please let me know why they are not present over. is there something still
>missing?
>Or i need install something else ( obviously excluding OS)?
>
>
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2005-02-13 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 7:27 LVM Multipathing shahid shaikh
2005-02-13 10:28 ` Christophe Varoqui
2005-02-13 11:29 ` shahid shaikh
2005-02-13 11:53 ` Christophe Varoqui [this message]
2005-02-14 5:06 ` shahid shaikh
2005-02-14 5:56 ` LVM Targets shahid shaikh
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=420F3F9C.3050809@free.fr \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=shahid.shaikh@patni.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.