From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Import LVM2 config from existing disk array?
Date: Fri, 20 May 2005 08:01:20 -0700 [thread overview]
Message-ID: <428DFBC0.3010003@starnetworks.us> (raw)
(I know this is slightly off-topic for this list, but I figured since
there are lots of SuSE experts here too it was worth a shot <G>)
I just converted a server over to SLES9 from another distro. This server
has a QLogic FC card, attached to an external array.
I had created a single PV on the array (no partition table, the whole
disk), and a VG using that PV.
When I attach the array to the SLES9 server, and go into the YaST2 LVM
tool, it shows the volume group and it's volumes, but only partially. It
has no idea what PVs the VG consists of, what the size is, etc. and the
VG is not started automatically on boot. This may be because nothing was
setup in the YaST2 Partitioner for this VG/PV, but I don't want to do
anything there for fear that it will be destructive.
How can I get the YaST2 LVM tool to "import" the configuration of the
existing PV/VG/LVs, so that it can be managed normally from that point
forward?
reply other threads:[~2005-05-20 15:01 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=428DFBC0.3010003@starnetworks.us \
--to=kpfleming@starnetworks.us \
--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.