linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Robert Osowiecki <robert.osowiecki@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Trouble with balancing physical volumes with pvmove
Date: Thu, 22 Dec 2022 18:00:53 +0100	[thread overview]
Message-ID: <CAPgkq_Xzz9XaburH7EzCmsZDXqdOuEtO-Exs285uSMz4P67eAw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 851 bytes --]

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!

[-- Attachment #1.2: Type: text/html, Size: 1046 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

             reply	other threads:[~2023-01-02  7:44 UTC|newest]

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

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=CAPgkq_Xzz9XaburH7EzCmsZDXqdOuEtO-Exs285uSMz4P67eAw@mail.gmail.com \
    --to=robert.osowiecki@gmail.com \
    --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).