archive mirror
 help / color / mirror / Atom feed
From: John Stoffel <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] Trouble with balancing physical volumes with pvmove
Date: Wed, 4 Jan 2023 19:12:04 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Can you give us the output of ‘pvs’ and’lvs’ so we can see your setup?  It’s also not quite clear what failed, a disk?  If so, which one?  

Do you have copy of the lvs and pvs output before your failure?  And what about cat /proc/partitions output as well.

Sent from my iPhone

> On Jan 2, 2023, at 2:44 AM, Robert Osowiecki <> wrote:
> Dear LVM list,
> I had several PV's with mainly raid10 volumes. When one of them failed, I was able to recover with lvconvert --repair.
> After failed PV was replaced, it left me with a couple of filled up almost to 100% PV's and one 100% free. I'd like to create more raid10 volumes, but I'm unable to free any space...
> The following command (extents range cover one of rimage_N volumes) was only successful for one "meta" and one "rimage_0", but in all other cases fails like:
> [root@chimera ~]# pvmove /dev/sdg:0-15359 /dev/sdh
>   Insufficient free space: 15360 extents needed, but only 0 available
>   Unable to allocate mirror extents for vgkvm/pvmove0.
>   Failed to convert pvmove LV to mirrored.
> Why? There's certainly lots of free space on /dev/sdh, it's almost free!
> I don't want to be forced to use only linear volumes from now... please help!
> _______________________________________________
> linux-lvm mailing list
> read the LVM HOW-TO at

linux-lvm mailing list
read the LVM HOW-TO at

      reply	other threads:[~2023-01-05  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 17:00 [linux-lvm] Trouble with balancing physical volumes with pvmove Robert Osowiecki
2023-01-05  0:12 ` John Stoffel [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).