From: Scott Serr <serrs@theserrs.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] pvmove unable to move extents to multiple smaller pvs
Date: Wed, 29 Sep 2004 00:18:28 -0600 [thread overview]
Message-ID: <415A53B4.60001@theserrs.net> (raw)
I'm trying to use pvmove to shuffle things around. I have a pv with
22375 extents which I would like to remove from the system. I've added
two (2) pvs with 11194 extents each. I get an error message:
Insufficient contiguous allocatable extents (11194) for logical volume
pvmove0: 22375 required
Allocation for temporary pvmove LV
Now before you say, don't make it contiguous... It seems that it isn't
already.
# lvchange --contiguous n /dev/data_vg/data_lv
Allocation policy of logical volume "data_lv" is already not contiguous
Is this normal? Do I really need all that contiguous space on 1 pv?
Thanks in advance,
Scott Serr
next reply other threads:[~2004-09-29 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 6:18 Scott Serr [this message]
2004-09-29 20:02 ` [linux-lvm] pvmove unable to move extents to multiple smaller pvs Scott Serr
2004-09-29 20:20 ` Clint Byrum
2004-09-29 21:09 ` Scott Serr
2004-09-30 3:20 ` Scott Serr
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=415A53B4.60001@theserrs.net \
--to=serrs@theserrs.net \
--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