Bug 1494135

Summary:	Stripes handling for conversion of mirrored device needs review
Product:	[Community] LVM and device-mapper	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	Heinz Mauelshagen <heinzm>
lvm2 sub component:	Mirroring and RAID	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED UPSTREAM	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, heinzm, jbrassow, jo4rht, msnitzer, mtowey, nkshirsa, prajnoha, rleese, zkabelac
Version:	2.02.175	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-08 17:21:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1720705
Bug Blocks:

Description Zdenek Kabelac 2017-09-21 14:12:32 UTC

Description of problem:

As stated in bug 1483530 - lvconvert handling of 'stripes' argument does need extra look.

ATM argument passed to lvconvert looks mostly ignored.

It's unclear which logic we want to go for.

Do we want to let users create  'individual' legs striped ?

To which extent we want to make usage of 'mirrors'  and 'raid1' equal ?
(Possible new BZ ?)

If user had 'striped' targed in past - we allowed to mirror it while existing 'raid1' rejects such device from upconversion (only linears could be mirrored)

Old mirrors do take 'stripes' - yet they always let user create 'linears' for its legs (ignoring silently any option passed in for striping).

We should also reflect this in some way in man pages - where we currently suggest these --stripes & --stripesize options are actually acceptable for creation - yet one is directly prohibited and second is ignored.

In past - we accepted both option and silently ignored them - so commands the were at least creating  'some mirror' by older scripts are now rejected - in this case it's for deciding - whether we want to cause command rejection as 'error' fixing or we want to introduce command failure as regression.


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

How reproducible:


Steps to Reproduce:
1.  lvcreate   [-iX -Iy] -LBBB -n LV VG
2.  lvconvert -m 1  [--type mirror|raid1] [-iX -Iy] VG/LV
3.

Actual results:


Expected results:


Additional info:

Comment 7 Heinz Mauelshagen 2019-07-08 17:21:08 UTC

Closing in lieu of 1720705

Comment 8 Joachim Wagner 2022-03-30 15:54:04 UTC

1720705 does not discuss the overall picture, only the specific problem of a regression in the CLI. Suggest re-opening this one for visibility.