Bug 1250627 – lvcreate --type raid1 -m 1 -l 90%vg -n cache0 vgcache.0 /dev/sda /dev/sdd # takes up all 100%

Bug 1250627 - lvcreate --type raid1 -m 1 -l 90%vg -n cache0 vgcache.0 /dev/sda /dev/sdd # takes up all 100%

Summary:	lvcreate --type raid1 -m 1 -l 90%vg -n cache0 vgcache.0 /dev/sda /dev/sdd # t...

Status:	NEW

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	lvm2 (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Alasdair Kergon
QA Contact:	cluster-qe@redhat.com
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-05 11:25 EDT by lejeczek
Modified:	2017-08-02 02:49 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description lejeczek 2015-08-05 11:25:52 EDT

Description of problem:

is this normal? Does -l work?
Only if I specify size with -L 200G I see free PEs in VG.

Version-Release number of selected component (if applicable):

lvm2-2.02.115-3.el7_1.1.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Marian Csontos 2015-08-10 11:28:12 EDT

Yes, `-l` works: it is specifying the approximate size of the LV created not the total space consumed. In this case 2 90%vg RAID legs are created, and LVM correctly caps that at 100%.

Comment 3 Marian Csontos 2015-08-10 11:36:49 EDT

Hmmm, seems it "works" and after all it IS a bug:

> When expressed as a  percentage, the  number  is  treated  as  an
> approximate  upper  limit for the total number of physical extents to be
> allocated (including extents used by any mirrors, for example).

Note You need to log in before you can comment on or make changes to this bug.