Has anyone had any luck getting evms to work with dm-crypt?
I can create a mapping and get it to show up in /dev/mapper, but evms
doesn't see it. I have tried editing the emvs.conf file to scan 'mapper'
also in /dev but it doesn't seem to help...
From: Kevin Corry <kevcorry@us...> - 2004-12-13 14:28:56
On Monday 13 December 2004 2:28 am, Alex wrote:
> Has anyone had any luck getting evms to work with dm-crypt?
> I can create a mapping and get it to show up in /dev/mapper, but evms
> doesn't see it. I have tried editing the emvs.conf file to scan 'mapper'
> also in /dev but it doesn't seem to help...
Are you trying to build volumes on top of encrypted devices? If so, then that
setup isn't currently supported. Right now, the only DM devices that EVMS
allows as disks are DM-Multipath devices. Since EVMS creates DM devices,
allowing all DM devices to be discovered as disks would cause duplicates
Most people using EVMS and dm-crypt first create EVMS volumes and then encrypt
those volumes with dm-crypt. Because of this, we haven't really spent any
time on the reverse scenario. However, that doesn't mean it wouldn't be
possible. As I said, we already have special case code to allow some
dm-multipath devices, so it wouldn't be too hard to do the same thing for
dm-crypt. And since we don't have an encryption plugin for EVMS, there
shouldn't be any danger of conflicts during discovery. However, right now
we're trying to get ready for the 2.5.0 release, so I won't have time to look
into this until after that release is out.
But, there is something you could do in the meantime. EVMS *does* support loop
devices as disks, so you could create a loop device on your dm-crypt device
(using losetup). Then run EVMS and it should see loop0 as a disk and you can
create volumes on it. Then, if/when I get the above EVMS-on-dm-crypt support
in, you could simply remove the intermediate loop device.
Hope that helps!