From: Milan Broz <mbroz@redhat.com>
To: Alvin Thompson <alvin@thompsonlogic.com>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] how to determine the mapped device from the original device
Date: Thu, 10 Dec 2009 08:35:34 +0100 [thread overview]
Message-ID: <4B20A4C6.1010207@redhat.com> (raw)
In-Reply-To: <6F8A7585-60EB-4844-90B9-06EE3BB2A76E@thompsonlogic.com>
On 12/10/2009 01:37 AM, Alvin Thompson wrote:
> I was wondering if it is possible to determine the mapped device from the original device. For example, if you used the command:
>
> cryptsetup luksOpen /dev/sdd1 backup
>
> Can you later determine the mapped device name ('backup' in this case) if all you know is the device (/dev/sdd1)?
For really low-level, you can try dmsetup.
If you know the major:minor of that device (ls -l /dev/sdd1) check "dmsetup ls --tree" or similar.
The reverse is "cryptsetup status backup" and see device there.
All active encrypted devices you can see with "dmsetup status --target crypt" (or dmsetup table and check table directly).
Anyway, this seems like good idea to add some new command to cryptsetup, like "cryptsetup deps <dev>" to display
encrypted device mapped to underlying <dev>... add new issue to project page if you want this please.
Milan
--
mbroz@redhat.ocm
next prev parent reply other threads:[~2009-12-10 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 0:37 [dm-crypt] how to determine the mapped device from the original device Alvin Thompson
2009-12-10 1:20 ` Uwe Menges
2009-12-10 7:35 ` Milan Broz [this message]
2009-12-11 4:17 ` Arno Wagner
2009-12-11 9:15 ` Mario 'BitKoenig' Holbe
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=4B20A4C6.1010207@redhat.com \
--to=mbroz@redhat.com \
--cc=alvin@thompsonlogic.com \
--cc=dm-crypt@saout.de \
/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.