10 Commits

Author	SHA1	Message	Date
Zdenek Kabelac	c838e79cd2	tests: fix for new hardened bash ... Add missing get_devs. When $7 is not given use empty string. See if we can live with less RAM disk for PVs. Drop limitation on single core as presence 1.12 should address this.	2017-07-12 18:05:56 +02:00
Zdenek Kabelac	e68d986cd5	tests: check result directly	2017-07-10 14:23:53 +02:00
Zdenek Kabelac	160cb1e713	tests: replace cat usage	2017-07-10 14:23:53 +02:00
Zdenek Kabelac	e55bae2b2c	tests: use bash	2017-07-10 14:23:53 +02:00
Zdenek Kabelac	535f7209d2	tests: request 1.12 for reshaping raid ... We will need 1.12 as the kernel needs some mandatory md fixes, otherwise random freezes may appear.	2017-06-23 18:44:01 +02:00
Heinz Mauelshagen	d48b816764	test: also prevent lvconvert-raid-reshape.sh on single core	2017-04-21 02:17:55 +02:00
Heinz Mauelshagen	17bee733d1	raid: conditionally reject convert to striped/raid0* ... If SubLVs to be removed still exist after an image removing conversion (i.e. "lvconvert --yes --force --stripes N " with N < total stripes) any request to convert to a different striped/raid* level has to be rejected until after those freed SubLVs got removed by running the aforementioned lvconvert again. Add tests to check conversion to striped/raid* gets rejected. Enhance a test comment. Related: rhbz1191935 Related: rhbz1366296	2017-03-17 13:58:54 +01:00
Heinz Mauelshagen	76b843a4bf	test: adjust to proper dm-raid target version ... Adjust to final target version 1.10.1 supporting reshape properly and to recently changed report field specifications (e.g. rehape_len_le) to allow these tests to run. Lower mirror region size to suite the tiny test VG.	2017-03-16 21:17:58 +01:00
Heinz Mauelshagen	48778bc503	lvconvert: add new reporting fields for reshaping ... During an ongoing reshape, the MD kernel runtime reads stripes relative to data_offset and starts storing the reshaped stripes (with new raid layout and/or new stripesize and/or new number of stripes) relative to new_data_offset. This is to avoid writing over any data in place which is non-atomic by nature and thus be recoverable without data loss in the transition. MD uses the term out-of-place reshaping for it. There's 2 other areas we don't have report capability for: - number of data stripes vs. total stripes (e.g. raid6 with 7 stripes toal has 5 data stripes) - number of (rotating) parity/syndrome chunks (e.g. raid6 with 7 stripes toal has 2 parity chunks; one per stripe for P-Syndrome and another one for Q-Syndrome) Thus, add the following reportable keys: - reshape_len (in current units) - reshape_len_le (in logical extents) - data_offset (in sectors) - new_data_offset ( " ) - data_stripes - parity_chunks Enhance lvchange-raid.sh, lvconvert-raid-reshape-linear_to_striped.sh, lvconvert-raid-reshape-striped_to_linear.sh, lvconvert-raid-reshape.sh and lvconvert-raid-takeover.sh to make use of new keys. Related: rhbz834579 Related: rhbz1191935 Related: rhbz1191978	2017-03-01 18:50:35 +01:00
Heinz Mauelshagen	76f60cc430	lvconvert: add missed new test scripts for reshaping ... Add aforementioned but forgotten new test scripts lvconvert-raid-reshape-linear_to_striped.sh, lvconvert-raid-reshape-striped_to_linear.sh and lvconvert-raid-reshape.sh Those presume dm-raid target version 1.10.2 provided by a following kernel patch. Related: rhbz834579 Related: rhbz1191935 Related: rhbz1191978	2017-02-24 05:20:59 +01:00