Quote:
Originally Posted by avallach
actually it's Arch ;-)
|
Ah yeah I always forget there's something else than debian
Quote:
and yes dm_crypt is loaded. So it's rather a bug :/
|
Yes but where is the question!
Quote:
hope they'll do something with it soon..
|
They won't if they are not aware of it. The page that I showed you says it was corrected by a kernel upgrade. Looking quickly at kernel changelog, I haven't seen the change.
You do run the _latest_ 2.6.x ? Like 2.6.18.4 or 2.6.x.latest
Quote:
oh... almost forgot, when using Debian Etch I can easily access my data there is cryptsetup 1.0.5 (I wonder why it isn't on official cryptsetup page ) in Etch, so maybe after upgrading my cryptsetup this problem will be solved...
|
1.0.5 doesn't exist ?? see here:
http://packages.debian.org/cgi-bin/s...ll&release=all
which is based on upstream cryptsetup version:
http://packages.debian.org/changelog...26-1/changelog
http://bugs.debian.org/cgi-bin/versi...%3A1.0.4~rc2-1
My method would be to upgrade first the kernel (in case you don't have the latests) because running a buggy kernel is never perfect.
And then maybe cryptsetup needs to be updated for compatibility with the newer dm_crypt or dm_mapper.
ioctl are a way to communicate to the kernel module. It looks like the cryptsetup is not compatible with the kernel (bad argument).
When you get the same Device Mapper (kernel in fact) and cryptsetup versions then it should work the same..