From: runappz <runappz@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes')
Date: Wed, 18 Jul 2018 22:41:14 +0800 [thread overview]
Message-ID: <80dbc3e4-3f7e-ba5d-7f0b-00b809098538@gmail.com> (raw)
In-Reply-To: <20180718141506.GD12563@bogon.ca>
Thank you for clarifying it sir. Then for `-l 8` I expect all
`lvolX_rimage_N`s has 4 extents rather than 8:
--- Segments ---
Logical extents 0 to 7:
Type raid10
Monitoring monitored
Raid Data LV 0
Logical volume lvol5_rimage_0
Logical extents 0 to 7
Raid Data LV 1
Logical volume lvol5_rimage_1
Logical extents 0 to 7
...
On 2018/7/18 22:15, Douglas Paul wrote:
> On Wed, Jul 18, 2018 at 09:25:37PM +0800, runappz wrote:
>> lvcreate --type raid10 -m 1 -i 2 -l 24576 pve # created lvol1
>> lvcreate --type raid10 -m 1 -i 2 -l 8 pve # created lvol2
>> lvcreate --type raid10 -m 1 -i 2 -l 8 pve # created lvol3
>>
>> lvcreate --type raid10 -m 1 -i 2 -l 8 pve # created lvol4
>> lvcreate --type raid10 -m 1 -l 8 pve # created lvol5
>>
>> The default LE size was 4MiB, so that I expect lvol1 to be 2*4*24576
>> MiB, while other 4 are all 2*4*8 MiB. However, I only got 4*24576 MiB
>> and 4*8 MiB partitions. I tried to run `mkfs.ext4` on lvol3 and mount
>> it. `df` shows clearly that lvol3 is a 32MiB volume.
> The -l option is the final size of the LV, not the space used on each device
> for each stripe or mirror. So when you say -l 8, it means the LV has 8
> usable extents, so it is supposed to be 32MiB. It doesn't matter how many
> stripes or mirrors you have.
>
next prev parent reply other threads:[~2018-07-18 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:25 [linux-lvm] Got only half the space of RAID10 LV with 4 PVs (similar to RAID1 cause LV shows it has 4 'Mirrored volumes') runappz
2018-07-18 14:15 ` Douglas Paul
2018-07-18 14:41 ` runappz [this message]
2018-07-19 11:33 ` Douglas Paul
-- strict thread matches above, loose matches on Subject: below --
2018-07-17 18:35 Ben Ma
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=80dbc3e4-3f7e-ba5d-7f0b-00b809098538@gmail.com \
--to=runappz@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).