3 Commits

Author	SHA1	Message	Date
Jonathan Brassow	2691f1d764	RAID: Make RAID single-machine-exclusive capable in a cluster ... Creation, deletion, [de]activation, repair, conversion, scrubbing and changing operations are all now available for RAID LVs in a cluster - provided that they are activated exclusively. The code has been changed to ensure that no LV or sub-LV activation is attempted cluster-wide. This includes the often overlooked operations of activating metadata areas for the brief time it takes to clear them. Additionally, some 'resume_lv' operations were replaced with 'activate_lv_excl_local' when sub-LVs were promoted to top-level LVs for removal, clearing or extraction. This was necessary because it forces the appropriate renaming actions the occur via resume in the single-machine case, but won't happen in a cluster due to the necessity of acquiring a lock first. The *raid* tests have been updated to allow testing in a cluster. For the most part, this meant creating devices with '-aey' if they were to be converted to RAID. (RAID requires the converting LV to be EX because it is a condition of activation for the RAID LV in a cluster.)	2013-09-10 16:33:22 -05:00
Zdenek Kabelac	cd9350198e	tests: drop testing of raids in cluster ... Since raid is not clustered yet - drop it from testing in cluster phase. (saving running some time)	2013-05-30 17:35:23 +02:00
Zdenek Kabelac	93d7d3ed2c	test: split raid tests ... Separate original raid test and new raid10 test, so the old could be tested on platforms without raid10 support. Replace test-unfriendly `ls /dev/mapper` with dmsetup ls	2012-10-09 12:22:26 +02:00