All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Nicollet <nicollet@jeru.org>
To: dm-crypt@saout.de
Subject: [dm-crypt] From /dev/mapper to the real device
Date: Tue, 18 Jan 2011 10:01:49 +0100	[thread overview]
Message-ID: <20110118090149.GE14608@jeru.org> (raw)

Hi,

I have searched through the manuals without finding an answer.

I did something like that:
cryptsetup luksOpen /dev/mapper/lv_device crypto_device

I would like to find a way, given /dev/mapper/crypto_device, to find
which lv_device it was built from.

Is there a command or a way to find this information back ?
A sort of mount command for the dm-crypt.

Thank you very much,

Cheers,

-- 
Xavier Nicollet

             reply	other threads:[~2011-01-18  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  9:01 Xavier Nicollet [this message]
2011-01-18  9:34 ` [dm-crypt] From /dev/mapper to the real device Milan Broz
2011-01-18 14:25   ` Arno Wagner
2011-01-18 16:31     ` Thomas Bächler
2011-01-18 15:38   ` [dm-crypt] Another corrupt luks header thread Viktor Ekmark
2011-01-18 16:36     ` Thomas Bächler
2011-01-18 18:54     ` Arno Wagner

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=20110118090149.GE14608@jeru.org \
    --to=nicollet@jeru.org \
    --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.