From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: lejeczek <peljasz@yahoo.co.uk>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] stripped LV with segments vs one segment
Date: Mon, 10 Apr 2017 16:19:40 +0200 [thread overview]
Message-ID: <18cefd41-2c11-5655-a117-2572b1bc4b7a@gmail.com> (raw)
In-Reply-To: <3e790d03-8da8-13c4-d1d3-e1f5f7b3c6f9@yahoo.co.uk>
Dne 10.4.2017 v 13:16 lejeczek napsal(a):
>
>
> On 10/04/17 12:03, Zdenek Kabelac wrote:
>> Dne 10.4.2017 v 11:29 lejeczek napsal(a):
>>> hi there
>>>
>>> I could not extend my stripped LV, had 3 stripes and wanted to add one more.
>>> Only way LVM let me do it was where I ended up with this:
>>>
>>> --- Segments ---
>>> Logical extents 0 to 751169:
>>> Type striped
>>> Stripes 3
>>> Stripe size 16.00 KiB
>>> Stripe 0:
>>> Physical volume /dev/sdd
>>> Physical extents 0 to 250389
>>> Stripe 1:
>>> Physical volume /dev/sde
>>> Physical extents 0 to 250389
>>> Stripe 2:
>>> Physical volume /dev/sdc
>>> Physical extents 0 to 250389
>>>
>>> Logical extents 751170 to 1001559:
>>> Type linear
>>> Physical volume /dev/sdf
>>> Physical extents 0 to 250389
>>>
>>> 1st question - was this really the only way LVM would extend?
>>> 2nd - is there performance penalty with segments like above vs one stripped
>>> segment?
>>>
>>
>> Hi
>>
>>
>> Not really sure what you aim to do.
>>
>> If you have LV segment with 3 stripes - you have to keep also extension
>> using 3 stripes - you can't have 1st. halve of LV spanning 3 disk and add
>> there a new LV segment as linear - as listed in this post.
>>
>> Both segments must by striped.
>>
>> Regards
>>
>> Zdenek
>
> 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.
> 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
You can't request stripe 4 (needs 4 disks) and pass just single /dev/sdf
device.
Zdenek
prev parent reply other threads:[~2017-04-10 14:19 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
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 [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:
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=18cefd41-2c11-5655-a117-2572b1bc4b7a@gmail.com \
--to=zdenek.kabelac@gmail.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).