linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: David Teigland <teigland@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] (resend) may bug: lvconvert reports "Insufficient free space" when doing "--replace"
Date: Thu, 18 Nov 2021 19:18:52 +0100	[thread overview]
Message-ID: <CAM23VxpwpJ+dkYtWgufVrv1ryx802Dygd1b5qYp-QDrwL-xiRQ@mail.gmail.com> (raw)
In-Reply-To: <f8a0b5c1-7b07-d119-5ce0-4fae51123ceb@suse.com>


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

Hemng,

'lvconvert --replace ..." reports the new PV does  not have enough space
(89 needed/49 available) to suit full replacement and rejects as
replacement requires complete SubLVs to move off respective PVs.

Check lsblk (or lvs -ao+devices) after the pvmove to confirm a partial move
across resulting remaining allocations for leg 0 on /dev/sdh, i.e no
replacement

Use a larger PV to be able to replace.

Best,
Heinz

On Mon, Nov 8, 2021 at 7:46 AM heming.zhao@suse.com <heming.zhao@suse.com>
wrote:

> (I sent this mail some days before, it looks this mail was blocked by
> anti-spam system. resend it)
>
> Hello list,
>
> I may found a bug, when lv is raid1, and each leg includes more than one
> PV.
>
> When doing "lvconvert --replace" to replace one of the oldpv with a newpv,
> It looks lvconvert requires full raid array size for a single newpv.
>
> lvm version: 2.03.12, Reproducible steps:
>
> ```
> # vgcreate vg1 /dev/sdg /dev/sdh
>    Volume group "vg1" successfully created
>
> # lvcreate -n lv1 -l 90%FREE vg1
>    Logical volume "lv1" created.
>
> # vgextend vg1 /dev/sdj /dev/sdk
>    Physical volume "/dev/sdj" successfully created.
>    Physical volume "/dev/sdk" successfully created.
>    Volume group "vg1" successfully extended
>
> # lvconvert --type raid1 vg1/lv1 /dev/sdg /dev/sdh /dev/sdj /dev/sdk
> Are you sure you want to convert linear LV vg1/lv1 to raid1 type? [y/n]: y
>    Logical volume vg1/lv1 successfully converted.
>
> # lsblk
> NAME               MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> sdg                  8:96   0  200M  0 disk
> └─vg1-lv1_rimage_0 254:4    0  352M  0 lvm
>    └─vg1-lv1        254:2    0  352M  0 lvm
> sdh                  8:112  0  200M  0 disk
> ├─vg1-lv1_rmeta_0  254:3    0    4M  0 lvm
> │ └─vg1-lv1        254:2    0  352M  0 lvm
> └─vg1-lv1_rimage_0 254:4    0  352M  0 lvm
>    └─vg1-lv1        254:2    0  352M  0 lvm
> sdi                  8:128  0  200M  0 disk
> sdj                  8:144  0  200M  0 disk
> ├─vg1-lv1_rmeta_1  254:5    0    4M  0 lvm
> │ └─vg1-lv1        254:2    0  352M  0 lvm
> └─vg1-lv1_rimage_1 254:6    0  352M  0 lvm
>    └─vg1-lv1        254:2    0  352M  0 lvm
> sdk                  8:160  0  200M  0 disk
> └─vg1-lv1_rimage_1 254:6    0  352M  0 lvm
>    └─vg1-lv1        254:2    0  352M  0 lvm
> sdl                  8:176  0  200M  0 disk
>
> # vgextend vg1 /dev/sdi
>    Volume group "vg1" successfully extended
>
> # lvconvert --replace /dev/sdh vg1/lv1 /dev/sdi  (<=== failed, should
> succeed)
>    Insufficient free space: 89 extents needed, but only 49 available
>    LV vg1/lv1 in not partial.
>
> # lvconvert --replace /dev/sdg vg1/lv1 /dev/sdi   (<=== failed, should
> succeed)
>    Insufficient free space: 89 extents needed, but only 49 available
>    LV vg1/lv1 in not partial.
>
> # pvmove /dev/sdh /dev/sdi
>    /dev/sdh: Moved: 2.50%
>    /dev/sdh: Moved: 100.00%
> ```
>
> pvmove is workable, but I think it's a work around.
> lvconvert should run successfully with above cmds.
>
> Thanks,
> Heming
>
>
> _______________________________________________
> 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/

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

[-- Attachment #2: Type: text/plain, Size: 201 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:[~2021-11-19  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 12:44 [linux-lvm] may bug: lvconvert reports "Insufficient free space" when doing "--replace" heming.zhao
2021-11-07  8:08 ` [linux-lvm] (resend) " heming.zhao
2021-11-18 18:18   ` Heinz Mauelshagen [this message]
2021-11-22  7:52     ` heming.zhao

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=CAM23VxpwpJ+dkYtWgufVrv1ryx802Dygd1b5qYp-QDrwL-xiRQ@mail.gmail.com \
    --to=heinzm@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=teigland@redhat.com \
    --cc=zkabelac@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).