Dr. Uwe Meyer-Gruhl wrote:
It seems that this special use-case (i.e. using crypto over raid) is simply the main scenario to trigger the incompatibility between device mapper and raid subsystems. Who would care to use device mapper over raid if not for encryption?
For LVM over RAID?
BTW: Are there known problems with LVM and RAID? And has anyone tested with 2.6.17 (although as far as I remember, the changes from 2.6.16 were made to enable RAID-5 online growing of arrays and not for bugfixing).
I've had intermittent problems running VMWare on LVM on RAID1. The volume doesn't get corrupted pe se, but it does turn the volume read-only, which is very annoying when the volume is /home. Sometimes it would happen before the VMWare guest machine booted, other times it could run for about 50 minutes(Garmin Mapsource takes about 55 minutes to load my GPS with a new set of maps).
I'd written the issue off as a flaky disk controller (since it the frequency was reduced after a BIOS upgrade). When it recurred, I moved my VMWare machines to an external USB HDD, and didn't pursue the issue anymore. However, this thread reminds me of the issue.
-Luke
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
