From: Louis Guillaume <lguillaume@berklee.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Stability of pvresize
Date: Sat, 02 Dec 2006 12:18:39 -0500 [thread overview]
Message-ID: <4571B56F.9050506@berklee.edu> (raw)
Hi,
I've seen a couple messages recently about pvresize. Since I'm about to
implement a system that might depend on this functionality, I'd like to
know whether it works well!!!
Here's the scenario:
. Using an San.
. A meta-LUN is created consisting of 2 `real' LUNs.
. Meta-LUN is incorporated as a PV on the Linux Host.
. We add a third LUN to the meta-LUN on the SAN.
This is where pvresize is supposed to come in. Once the PV is resized,
is the VG automatically aware of the new PEs? Are there any pitfalls in
this scheme?
The alternative is to not use meta-LUNs and just add a new PV as needed
and vgextend. But this puts more work on the server's CPU. Opinions?
Louis
next reply other threads:[~2006-12-02 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 17:18 Louis Guillaume [this message]
2006-12-03 21:06 ` [linux-lvm] Stability of pvresize Zac Slade
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=4571B56F.9050506@berklee.edu \
--to=lguillaume@berklee.edu \
--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.