From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] pvdisplay -m
Date: Wed, 21 Jun 2006 12:52:09 +0200 [thread overview]
Message-ID: <449924D9.9090007@conterra.de> (raw)
is "pvdisplay -m" still unimplemented?
After I turned to a hardware raid5 system my PVs become
quite HUGE (about 2-4 TB each!). This huge PVs easily
get fragmented. If I want to pvmove some LV it often does not
work by default. The huge PV has space to hold the additional
LV, but it is not contiguous, and "--alloc anywhere" won't
split a contiguous chunk to fit into smaller gaps. (and the
algorithm to do so is not trivial, even if it sounds easy).
So I frequently end up with a desk calculator to analyze my
/etc/lvm/backup/ metadata to extract a list of occupied and
free ranges on my PV to express pvmove commands with explicit
PE ranges.
To make this easier, I would propose the following extensions:
Some command/option to print out the layout of a PV including
the free gaps.
Extend the --units option to display LE counts. (one could use "e",
but I don't know, how long it takes until we need to express sizes
as exabytes :-)
Express LE ranges by a "+" like /dev/sda:1000+500 as a shortcut
for /dev/sda:1000-1499.
btw: is there a more detailed description about how pvmove exactly
behaves when giving multiple source and/or target ranges?
--> can I explicitly express the splitting of source chunks into
target fragments by a single pvmove command?
If someone agrees that this is useful, I may start trying to
implement this and propose some patches.
Dieter.
reply other threads:[~2006-06-21 10:52 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=449924D9.9090007@conterra.de \
--to=stueken@conterra.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).