On Thu, February 8, 2007 22:51, Johannes Schlumberger said:
I built the packages and installed them.
The attached file contains the generated stderr stream (which looks a bit
strange to me). Just to make shure, here is also the output generated from
the command without the redirection.
Could
Hi,
Could you build a new kernel which includes the patch attached to bug
report #304507 and try again?
http://bugs.debian.org/cgi-bin/bugreport.cgi/2.6-bd-claim.patch?bug=304507;msg=5;att=1
It sems the same to me. This is kernel -asso-50 (I attached the config to the
inital bugreport mail)
Hi,
I just want to point out, so far after each test I brought the system back
into the beginning state (kernel, dmsetup-package, etc).
regards,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
I just want to point out, so far after each test I brought the system back
into the beginning state (kernel, dmsetup-package, etc).
Yes, that's good.
I just wanted to make shure, we are stil talking about the same setup :)
Could you please try a new compile, this time, skip the
On Fri, February 9, 2007 14:42, Johannes Schlumberger said:
Hi,
I just want to point out, so far after each test I brought the system back
into the beginning state (kernel, dmsetup-package, etc).
Yes, that's good.
Could you please try a new compile, this time, skip the previously
mentioned
On Fri, February 9, 2007 16:58, Johannes Schlumberger said:
Could you please try a new compile, this time, skip the previously
mentioned patch and instead do the following changes:
In fs/block_dev.c, add the following at the end of the function
bd_claim()
(just before the return):
Hi,
Meanwhile, could you add the following to the above mentioned debugging
output:
printk(dumping stack for %s:\n, current-comm);
dump_stack();
(right after the above printk in bd_claim())
And then send another dmesg this way...this should tell us which
process/kernel thread it is
On Fri, Feb 09, 2007 at 07:35:46PM +0100, Johannes Schlumberger wrote:
Hi,
Meanwhile, could you add the following to the above mentioned debugging
output:
printk(dumping stack for %s:\n, current-comm);
dump_stack();
(right after the above printk in bd_claim())
And then send another dmesg
Hi,
Thanks, this looks mighty suspicious...it looks like /dev/md0 is mounted
as your root partition by the initramfs? Please provide me with ls -al
/dev/root and cat /proc/cmdline as well as the contents of your grub
or lilo config file.
I am so sorry for stealing yours and other persons
reassign 409875 libdevmapper1.02
retitle 409875 libdevmapper should provide more helpful error messages
severity 409875 minor
thanks
On Fri, Feb 09, 2007 at 09:44:32PM +0100, Johannes Schlumberger wrote:
Thanks, this looks mighty suspicious...it looks like /dev/md0 is mounted
as your root
On Wed, February 7, 2007 22:31, Johannes Schlumberger said:
Hi,
Ok, could you create a file called e.g. map containing the following
line:
0 1 crypt aes-cbc-essiv:sha256 0123456789abcdef0123456789abcdef 0
/dev/md0 0
shure.
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt
Hi,
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt aes-cbc-essiv:sha256 \
0123456789abcdef0123456789abcdef 0 /dev/md0 0' map
[22:28:[EMAIL PROTECTED]:/tmp]# dmsetup create root map
device-mapper: reload ioctl failed: Invalid argument
Command failed
Could you try this again with
On Thu, Feb 08, 2007 at 07:52:53PM +0100, Johannes Schlumberger wrote:
Hi,
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt aes-cbc-essiv:sha256 \
0123456789abcdef0123456789abcdef 0 /dev/md0 0' map
[22:28:[EMAIL PROTECTED]:/tmp]# dmsetup create root map
device-mapper: reload ioctl
On Wed, Feb 07, 2007 at 12:51:52AM +0100, Johannes Schlumberger wrote:
Hi,
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
Hi,
Ok, could you create a file called e.g. map containing the following line:
0 1 crypt aes-cbc-essiv:sha256 0123456789abcdef0123456789abcdef 0
/dev/md0 0
shure.
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt aes-cbc-essiv:sha256 \
0123456789abcdef0123456789abcdef 0 /dev/md0 0' map
On Wed, Feb 07, 2007 at 10:31:27PM +0100, Johannes Schlumberger wrote:
Hi,
Ok, could you create a file called e.g. map containing the following line:
0 1 crypt aes-cbc-essiv:sha256 0123456789abcdef0123456789abcdef 0
/dev/md0 0
shure.
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt
Hi,
This would suggest that the problem is not with cryptsetup at least.
Something seems wonky with device-mapper in general.
Whom should I be talking to about this?
Just to make sure, do you think you could install the Debian packaged
kernel, boot it and try to setup the mapping with
Hi,
Also...which device is / on? I.e. /dev/root is an alias of
/dev/hdwhat?
It is hdd6 at the moment, i am going to copy it back to md0 once i got the
cryptlayer on it working.
regards,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
[23:24:[EMAIL PROTECTED]:/home/spjsschl]# dmsetup table
swap2: 0 995967 crypt aes-cbc-plain
8fd07cf5cecac858cdd2c0ce673449b4c1734cecbe8a24e5be629d542c975cf1 0 22:5 0
swap1: 0 6458067 crypt aes-cbc-plain
dde5fec1ee7146100bc83af997171ce196c2d1c453134d21e574f85ccc296588 0 22:65 0
Which
On Wed, Feb 07, 2007 at 11:26:16PM +0100, Johannes Schlumberger wrote:
[23:24:[EMAIL PROTECTED]:/home/spjsschl]# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,data=ordered 0 0
Also...which device is / on? I.e. /dev/root is an alias of
/dev/hdwhat?
--
David Härdeman
On Wed, Feb 07, 2007 at 11:26:16PM +0100, Johannes Schlumberger wrote:
Hi,
This would suggest that the problem is not with cryptsetup at least.
Something seems wonky with device-mapper in general.
Whom should I be talking to about this?
That would be the dmsetup package maintainer, but lets
Hi,
And while we're at it, cat /proc/partitions to make sure that the
kernel and fdisk agree on partition sizes.
[01:53:[EMAIL PROTECTED]:/home/spjsschl]# cat /proc/partitions
major minor #blocks name
22 0 160086528 hdc
22 1 19543041 hdc1
22 29775552 hdc2
22
On Thu, Feb 08, 2007 at 01:49:35AM +0100, David Härdeman wrote:
Ok, one more test...could you deallocate both swap mappings and then try
to setup your root mapping?
That is, run something like
swapoff -a cryptsetup remove swap1 cryptsetup remove swap2
and then try the cryptsetup create...
Ok, one more test...could you deallocate both swap mappings and then try
to setup your root mapping?
That is, run something like
swapoff -a cryptsetup remove swap1 cryptsetup remove swap2
and then try the cryptsetup create... invocation
--
David Härdeman
Hi,
Ok, one more test...could you deallocate both swap mappings and then try
to setup your root mapping?
[01:49:[EMAIL PROTECTED]:/home/spjsschl]# swapoff -a cryptsetup remove swap1
cryptsetup remove swap2 cryptsetup -c aes -s 256 -d /dev/stdin create root
/dev/md0 /key
Command failed:
Hi,
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
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
27 matches
Mail list logo
