From: Milan Broz <asi@seznam.cz>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] inconsistency in opening multiple mappers on the same device
Date: Fri, 01 Jun 2012 08:31:33 +0200 [thread overview]
Message-ID: <4FC861C5.3010105@seznam.cz> (raw)
In-Reply-To: <CAFnMBaTKyAy3=O5LBwFWr-chY_+Zu-tVUX7+vDAWnDah=kuc5g@mail.gmail.com>
On 06/01/2012 12:12 AM, .. ink .. wrote:
> It looks like by default, cryptsetup does not allow opening more than
> one mapper on the same device bu it only checks the mapper name, not
> the device behind the mapper and hence it allows opening of multiple
> mappers on the same device as long as they use a different mapper
> name.
No. Try it with real device. (Loop devices are strange, losetup
allows you to map more loopback devices to one file. It was
always the same here, try it with previous version...)
It is basically about this:
By default, cryptsetup require exclusive access to underlying device:
# echo xxx | src/cryptsetup create x /dev/sdb x
# echo xxx | src/cryptsetup create y /dev/sdb x
Cannot use device /dev/sdb which is in use (already mapped or mounted).
With --shared it allows to use the same (already used) underlying device
# echo xxx | src/cryptsetup create y /dev/sdb x --shared
Obviously you cannot have the same mapping name...
Milan
next prev parent reply other threads:[~2012-06-01 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 22:12 [dm-crypt] inconsistency in opening multiple mappers on the same device .. ink ..
2012-06-01 5:55 ` Arno Wagner
2012-06-01 12:47 ` .. ink ..
2012-06-01 13:00 ` Milan Broz
2012-06-01 6:31 ` Milan Broz [this message]
2012-06-01 10:52 ` Javier Juan Martínez Cabezón
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=4FC861C5.3010105@seznam.cz \
--to=asi@seznam.cz \
--cc=dm-crypt@saout.de \
--cc=mhogomchungu@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox