From: "David Härdeman" <david@hardeman.nu>
To: Johannes Schlumberger <asso@doriath.informatik.uni-erlangen.de>
Cc: 409875@bugs.debian.org, agk@redhat.com, dm-devel@redhat.com,
waldi@debian.org, pkg-lvm-maintainers@lists.alioth.debian.org
Subject: Bug#409875: cannot setup device-mapper mapping ontop of /dev/md* device
Date: Thu, 8 Feb 2007 23:43:33 +0100 [thread overview]
Message-ID: <20070208224333.GC9849@hardeman.nu> (raw)
In-Reply-To: <20070208215149.GL32661@doriath.informatik.uni-erlangen.de>
On Thu, Feb 08, 2007 at 10:51:50PM +0100, Johannes Schlumberger wrote:
>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.
The stderr stream is fine. When you run it without redirection, bash
will helpfully mask the null characters that are printed (which is not
done when they are redirected to a file).
However, everything looks ok after studying that file, the first two
ioctl's are executed (i.e. the device-mapper version is checked and the
"root" mapping name is reserved).
Then when it is time to pass the actual parameters for the mapping using
the "reload" ioctl, everything goes south. I'm quickly running out of
ideas what might cause this or what the best way to debug it would be.
So I'm CC:ing this mail to some different people with the hope that
someone other than me can spot the error.
Quoting from previous mails:
> [04:11:35][root@asso:/home/spjsschl]# cryptsetup -c aes -s 256 -d /dev/stdin
> create root /dev/md0 < /key
> Command failed: device-mapper: reload ioctl failed: Invalid argument
>
> [04:12:57][root@asso:/home/spjsschl]# dmesg | tail -n 3
> device-mapper: table: 253:2: crypt: Device lookup failed
> device-mapper: ioctl: error adding target to table
> device-mapper: ioctl: device doesn't appear to be in the dev hash table.
>
> [22:28:31][root@asso:/tmp]# echo '0 10000 crypt aes-cbc-essiv:sha256 \
> 0123456789abcdef0123456789abcdef 0 /dev/md0 0' > map
> [22:28:46][root@asso:/tmp]# dmsetup create root map
> device-mapper: reload ioctl failed: Invalid argument Command failed
Executive summary:
dmsetup / cryptsetup both fail to create a mapping on top of a raid
device (/dev/md0 in this case).
For much more details, see the bug report, any help appreciated:
http://bugs.debian.org/409875
--
David Härdeman
next parent reply other threads:[~2007-02-08 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070206214530.GA23506@hardeman.nu>
[not found] ` <20070206220221.GL1316@doriath.informatik.uni-erlangen.de>
[not found] ` <20070206234626.GA26196@hardeman.nu>
[not found] ` <20070206235151.GM1316@doriath.informatik.uni-erlangen.de>
[not found] ` <20070207212457.GA12135@hardeman.nu>
[not found] ` <20070207213127.GA32661@doriath.informatik.uni-erlangen.de>
[not found] ` <32476.145.64.134.242.1170938284.squirrel@www.hardeman.nu>
[not found] ` <20070208185253.GK32661@doriath.informatik.uni-erlangen.de>
[not found] ` <20070208213609.GA6406@hardeman.nu>
[not found] ` <20070208215149.GL32661@doriath.informatik.uni-erlangen.de>
2007-02-08 22:43 ` David Härdeman [this message]
2007-02-09 10:45 ` Bug#409875: cannot setup device-mapper mapping ontop of /dev/md* device Loïc Minier
2007-02-09 12:00 ` Bug#409875: [Pkg-cryptsetup-devel] " David Härdeman
2007-02-09 14:33 ` Henrique de Moraes Holschuh
[not found] ` <22206.145.64.134.242.1171025126.squirrel@www.hardeman.nu>
[not found] ` <20070209134251.GO32661@doriath.informatik.uni-erlangen.de>
[not found] ` <35325.145.64.134.242.1171035160.squirrel@www.hardeman.nu>
[not found] ` <20070209155857.GP32661@doriath.informatik.uni-erlangen.de>
[not found] ` <56504.145.64.134.242.1171044839.squirrel@www.hardeman.nu>
[not found] ` <20070209183546.GQ32661@doriath.informatik.uni-erlangen.de>
[not found] ` <20070209203247.GA5378@hardeman.nu>
[not found] ` <20070209204431.GR32661@doriath.informatik.uni-erlangen.de>
2007-02-09 21:28 ` Bug#409875: [Pkg-cryptsetup-devel] Bug#409875: bug #409875 David Härdeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070208224333.GC9849@hardeman.nu \
--to=david@hardeman.nu \
--cc=409875@bugs.debian.org \
--cc=agk@redhat.com \
--cc=asso@doriath.informatik.uni-erlangen.de \
--cc=dm-devel@redhat.com \
--cc=pkg-lvm-maintainers@lists.alioth.debian.org \
--cc=waldi@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.