From: Marian Csontos <mcsontos@redhat.com>
To: lejeczek <peljasz@yahoo.co.uk>, linux-lvm@redhat.com
Subject: Re: [linux-lvm] stripped LV with segments vs one segment
Date: Tue, 11 Apr 2017 19:37:36 +0200 [thread overview]
Message-ID: <96c8bb8b-7678-07cc-dea4-579c62a85c32@redhat.com> (raw)
In-Reply-To: <570e1a57-6b36-3f09-af6c-f147c728e217@yahoo.co.uk>
On 04/10/2017 04:27 PM, lejeczek wrote:
>
>
> On 10/04/17 13:27, Marian Csontos wrote:
>> 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.
>>
> convert from stipe to raid0 would not preserve stripe sizes? is this
> correct?
It should keep stripe size and if it does not it is a bug.
> nor it would:
>
> -I/--stripesize not allowed for LV dellH200.InternalB/0 when converting
> from striped to raid0.
As it says, the option is simply not allowed. Also it would be
meaningless - one can not change stripe size while converting stripe to
raid0. At least not in RHEL-7.3 (lvm2-2.02.166). This is supposed to
work in upstream/2.02.169, but keep in mind that is a new feature, and
it is altering data, so better keep a working backup.
>
> LVM version: 2.02.166(2)-RHEL7 (2016-11-16)
> Library version: 1.02.135-RHEL7 (2016-11-16)
> Driver version: 4.35.0
next prev parent reply other threads:[~2017-04-11 17:37 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 [this message]
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=96c8bb8b-7678-07cc-dea4-579c62a85c32@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).