By default pvmove allocates extents on pvs OTHER than the one they are
coming from. If you want to move extents around on the same PV, IIRC,
you have to pass --alloc anywhere, and explicitly specify destination
extents.
At any rate, this isn't really a bug. It is by design that you can not
I'm reopening this, because I'm having the exact same problem as Paulo.
I'm trying with Lucid 2.6.32-24-generic and LVM2 2.02.54-1ubuntu4. Is
anyone willing to take a quick look at this and determine if it's
something which can be fixed?
** Changed in: lvm2 (Ubuntu)
Status: Invalid = New
You should be able to use pvmove to move the offending physical extents
within the pv. IIRC, the magic incantation is:
pvmove -v /dev/whatever_your_pv_is_called
--
pvresize can't shrink PVs
https://bugs.launchpad.net/bugs/177350
You received this bug notification because you are a member of
Soren, I just tried this out and sadly am having no luck. I run 'pvmove
-v /dev/sdf1' (sdf1 is my pv) and the result I get is:
Finding volume group mermaid
No extents available for allocation
But clearly I have extents on the pv, as reported by pvdisplay:
--- Physical volume ---
PV Name
I should have also mentioned that my vg only has one pv in it. Perhaps
this is compounding the problem - there is no other pv in the group to
which I can move extents. But really all I want to do is coalesce the
extents on the existing pv so that I can physically shrink it.
--
pvresize can't
And pvmove won't let you do that?
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
pvresize can't shrink PVs
https://bugs.launchpad.net/bugs/177350
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed
