All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Problems resizing physical volume
Date: Wed, 14 Apr 2010 18:04:34 +0300	[thread overview]
Message-ID: <4BC5D982.8030205@redhat.com> (raw)
In-Reply-To: <4BC5D83D.7040600@redhat.com>

On 04/14/2010 05:59 PM, Avi Kivity wrote:
>
>>>> [root@violet-regb ~]# pvmove /dev/sda2:4704-4765 /dev/sda2:4384-4445
>>>>    No extents available for allocation
>>> At this point I gave up.  Is there any way to accomplish this?
>> pvmove normally is used to move segments off the pv to other pvs in
>> order to free up that pv for removal.  So it is failing since it can not
>> find space on other disks, since you limited its search to specific
>> extents on the same disk.  You need to add --alloc anywhere to stop it
>> from excluding the current disk from its search.  The need for this is
>> kind of silly given that you explicitly tell it where to move to, it
>> should probably be assumed, but isn't.
>
> I'll try it out.  Thanks.
>

It worked, but only after I removed the destination extent specification.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-04-14 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  9:42 [linux-lvm] Problems resizing physical volume Avi Kivity
2010-04-14 14:47 ` Phillip Susi
2010-04-14 14:59   ` Avi Kivity
2010-04-14 15:04     ` Avi Kivity [this message]
2010-04-14 15:14     ` Phillip Susi
2010-04-14 20:05   ` Stuart D. Gathman
2010-04-14 21:12     ` Phillip Susi
2010-04-14 21:28       ` Alasdair G Kergon
2010-04-14 21:57         ` Stuart D. Gathman
2010-04-14 22:27           ` Alasdair G Kergon
2010-04-24  1:39   ` Ron Johnson

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=4BC5D982.8030205@redhat.com \
    --to=avi@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@cfl.rr.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.