On Tue, Feb 06, 2007 at 11:02:21PM +0100, Johannes Schlumberger wrote:
Hi,
and thanks for the trace, the problem is indeed here:
>ioctl(3, DM_TABLE_LOAD, 0x80a2040) = -1 EINVAL (Invalid argument)
that means that "crypt" is not a valid device-mapper target.
That in turn means that dm-crypt was not loaded and could not be
dynamically loaded by the kernel.
As you should be able to observe from my sent kernel config i have built
dm_crypt into the kernel, therefore it cannot (and has not to) be loaded
as a module.
Sorry, I missed the attached kernel config.
Unfortunately I am not able to reproduce this. Using a qemu machine with
two virtual disks in a RAID set, the crypt mapping is setup correctly.
If I do make sure that the dm-crypt.ko module is not available, the
error messages and strace exactly match yours.
What output do you get from "dmsetup targets"?
--
David Härdeman
