From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] how to determine the mapped device from the original device
Date: Fri, 11 Dec 2009 05:17:34 +0100 [thread overview]
Message-ID: <20091211041734.GB6979@tansi.org> (raw)
In-Reply-To: <6F8A7585-60EB-4844-90B9-06EE3BB2A76E@thompsonlogic.com>
Here is a way (not pretty):
1. Get a list of all names in /dev/mapper via "dmsetup info"
2. Do a "cryptsetup status" for all of them
3. Search the device you want to know about in the output of 2.
Should be doable in Perl/Python in half an hour or so.
Arno
On Wed, Dec 09, 2009 at 07:37:26PM -0500, Alvin Thompson wrote:
> Hi,
>
> 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)?
>
> Thanks,
> Alvin
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2009-12-11 4:17 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
2009-12-11 4:17 ` Arno Wagner [this message]
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=20091211041734.GB6979@tansi.org \
--to=arno@wagner.name \
--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.