From: "Måns Rullgård" <mru@users.sourceforge.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: Resizing PV
Date: Mon Sep 22 06:49:01 2003 [thread overview]
Message-ID: <yw1xr829kps6.fsf@users.sourceforge.net> (raw)
In-Reply-To: 20030922123435.X2618@sistina.com
"Heinz J . Mauelshagen" <mauelshagen@sistina.com> writes:
>> Is it possible to reduce the size of a PV, freeing some space at the
>> end? I can make sure that the end is unused, of course.
>
> No such command implemented yet.
>
> Hack:
> you can use LVM2 and change the text format of the metadata by hand
> before running vgcfgrestore to store it back onto the PVs.
>
> If you want to follow this non-supported path, you want to take a
> copy of the original metadata file in /etc/lvm/backup/ to be able to
> back out gain.
I'm already using lvm2. I noticed the pvresize command, but it just
says it's not implemented yet. Any chance it will be some time soon?
As for editing the metadata, I'm a little confused about the meaning
of some fields. After running vgcfgbackup, I have this in the file:
physical_volumes {
pv0 {
id = "eZV4mb-jk4z-pyfm-tGbJ-mBSW-drRT-ZHtgmn"
device = "/dev/discs/disc0/part2" # Hint only
status = ["ALLOCATABLE"]
pe_start = 65920
pe_count = 1189 # 37.1562 Gigabytes
}
}
What is the meaning of the pe_start field? If I wanted to reduce the
size by, say, 1 GB, would it be correct to reduce pe_count by 32, the
PE size being 32 MB?
--
M�ns Rullg�rd
mru@users.sf.net
next prev parent reply other threads:[~2003-09-22 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 5:23 [linux-lvm] Resizing PV Måns Rullgård
2003-09-22 5:45 ` Heinz J . Mauelshagen
2003-09-22 6:49 ` Måns Rullgård [this message]
2003-09-22 8:06 ` [linux-lvm] " Heinz J . Mauelshagen
2003-09-22 8:14 ` Måns Rullgård
2003-09-22 8:25 ` Heinz J . Mauelshagen
2003-09-23 3:47 ` Måns Rullgård
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=yw1xr829kps6.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--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