mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-22 17:35:59 +03:00
de78e8eae7
On conversions between striped/raid0* and raid4, the kernel expects the dedicated raid4 parity SubLVs in the first segment area rather than in the last it's been allocated to, thus the data mapping ain't proper. Enhance lvconvert (lib/metadata/raid_manip.c) to shift the dedicated parity SubLVs on conversions from striped/raid0* to raid4 and vice-versa. In case of raid0_meta -> raid4 where the MD raid0 personality already has stored RAID array device positions in the superblocks, the MetaLVs have to be cleared so that the kernel doesn't fail validating the array positions after lvm has shifted them up by one. Add more tests to lvconvert-raid-takeover.sh including one to check for mapping flaws by converting a created raid4 with filesystem -> striped and fsck it. Whilst on it: - add missing direct striped -> raid4 conversion to the takeover array to avoid an intermim conversion from striped -> raid0* - clean up the takeover array - allow lvconvert to actually call lv_raid_convert() on all takeover requests in order to check parameters and display messages provided by takeover functions rather than just "...not supported" from within lvconvert - fix a typo Resolves: rhbz1386148 |
||
|---|---|---|
| .. | ||
| activate | ||
| cache | ||
| cache_segtype | ||
| commands | ||
| config | ||
| datastruct | ||
| device | ||
| display | ||
| error | ||
| filters | ||
| format1 | ||
| format_pool | ||
| format_text | ||
| freeseg | ||
| label | ||
| locking | ||
| log | ||
| lvmpolld | ||
| metadata | ||
| mirror | ||
| misc | ||
| mm | ||
| notify | ||
| properties | ||
| raid | ||
| replicator | ||
| report | ||
| snapshot | ||
| striped | ||
| thin | ||
| unknown | ||
| uuid | ||
| zero | ||
| Makefile.in | ||