From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Are there problems with same VG on same hard disk?
Date: Wed Apr 9 07:42:01 2003 [thread overview]
Message-ID: <20030409124155.GH1366@tykepenguin.com> (raw)
In-Reply-To: <20030409123606.GA1752@glorybox>
On Wed, Apr 09, 2003 at 02:36:06PM +0200, Kai Weber wrote:
> On Wed, Apr 09, 2003 at 01:32:43PM +0200, Anders Widman wrote:
>
> > Why would you want to do that? One of the major benefits with LVM is
> > that you do not have to divide your physical disks into partitions,
> > but to do that through LVM. Also, performance-wise it is not a good
> > idea to do what you suggested.
>
> I have removed Windows from a partition. So it is now empty and could be
> used an included in the VG. If it's possible to resize the partitions...
>
> /dev/hda7 1923 2520 4803403+ 8e Linux LVM
> /dev/hda8 2521 3198 5446003+ 8e Linux LVM
> /dev/hda9 3199 9729 52460226 8e Linux LVM
>
> /dev/hda7 is VG system, /dev/hda9 is VG data and /dev/hda8 the new and
> empty partition. I have no space to backup /dev/hda9 for merging hda8
> and hda9. There seems to be no "pvresize" for LVM1.
>
Sounds perfectly reasonable to me, that's pretty much what I have, though
without the shame of previously having windows on the machine :-)
PV /dev/sda7 VG vg00 lvm1 [20.00 GB / 0 free]
PV /dev/sda8 VG vg00 lvm1 [9.89 GB / 0 free]
PV /dev/sdb1 VG vg00 lvm1 [34.18 GB / 3.18 GB free]
...and yes, I swap to an LV too...
patrick
next prev parent reply other threads:[~2003-04-09 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 6:27 [linux-lvm] Are there problems with same VG on same hard disk? Kai Weber
2003-04-09 6:33 ` Anders Widman
2003-04-09 7:36 ` Kai Weber
2003-04-09 7:42 ` Patrick Caulfield [this message]
2003-04-09 6:39 ` Joe Thornber
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=20030409124155.GH1366@tykepenguin.com \
--to=caulfield@sistina.com \
--cc=linux-lvm@sistina.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