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):
Steps to Reproduce:
1. lvcreate [-iX -Iy] -LBBB -n LV VG
2. lvconvert -m 1 [--type mirror|raid1] [-iX -Iy] VG/LV
Closing in lieu of 1720705