From: Marian Csontos <mcsontos@redhat.com>
To: linux-lvm@redhat.com, peljasz@yahoo.co.uk
Subject: Re: [linux-lvm] stripped LV with segments vs one segment
Date: Mon, 10 Apr 2017 14:27:19 +0200 [thread overview]
Message-ID: <7242e565-8540-74c1-d7db-39e84d029bf1@redhat.com> (raw)
In-Reply-To: <3e790d03-8da8-13c4-d1d3-e1f5f7b3c6f9@yahoo.co.uk>
On 04/10/2017 01:16 PM, lejeczek wrote:
>
> I had 3 stripe LV, you know, three PVs, and wanted the LV to have 4
> stripes, wanted to add 4th PV, you can see it from above lvdisplay.
What you want is "reshape" not extend. This was committed as RAID
feature to 2.02.169, but it is still somewhat experimental. You would
need to convert stripe LV to RAID0 (aka takeover) and then reshape.
> I tried these and each time it errored:
> $ lvextend -v -i 4 -l+100%free dellH200.InternalB/0
> $ lvextend -v -i 4 -l+100%pv dellH200.InternalB/0 /dev/sdf
> $ lvextend -i 4 -l 100%vg dellH200.InternalB/0
>
lvextend With -i 4 this would add another striped segment with 4 devices
after the first segment - and IIUC you do not have enough space for that.
> I did have only one segment, an LV spanning 100%vg with 100%each-pv.
> And the above is the result of: $ lvextend -i 1 -l +100%free
> dellH200.InternalB/0 /dev/sdf
>
> so, either I'm not getting it right or a stripped LV cannot be extended
> this way - then: is there performance penalty with segments like above
> vs one stripped
> segment?
>
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2017-04-10 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 9:29 [linux-lvm] stripped LV with segments vs one segment lejeczek
2017-04-10 11:03 ` Zdenek Kabelac
2017-04-10 11:16 ` lejeczek
2017-04-10 12:27 ` Marian Csontos [this message]
2017-04-10 13:35 ` lejeczek
2017-04-11 17:16 ` Marian Csontos
2017-04-10 14:27 ` lejeczek
2017-04-11 17:37 ` Marian Csontos
2017-04-11 18:26 ` lejeczek
2017-04-10 14:19 ` Zdenek Kabelac
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=7242e565-8540-74c1-d7db-39e84d029bf1@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=peljasz@yahoo.co.uk \
/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).