From: Milan Broz <mbroz@redhat.com>
To: Michael Zabriskie <mgzabriskie@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] shared block devices
Date: Wed, 30 Mar 2011 23:03:04 +0200 [thread overview]
Message-ID: <4D939A88.70009@redhat.com> (raw)
In-Reply-To: <1301506184.6571.29.camel@occipital.ops.ut.us.attask.com>
On 03/30/2011 07:29 PM, Michael Zabriskie wrote:
> I have been able to gather that a shared block device type setup is not
> supported. I.E. luks + clvm + gfs2, luks + asm, or luks + ocfs2 shared
> across multiple servers. So what I am wondering is if this is on the
> road map or if there is another open source technology out there that
> can accomplish this?
If you have LUKS device and mapped (plaintext) device is exported
through iSCSI/DRBD or whatever to several cluster nodes, it will work
(and use some clustered fs, or maybe clvmd on top of that).
(IOW encryption run only on some master server.)
What you cannot do is to map the underlying device on several nodes
and run LUKS on every node separately (in parallel).
(In principle, with proper barrier/flush support and clustered
fs on top it, it should work but nobody tests and support these
configurations.)
Or you have to open exactly on one node and migrate it as service
(similar to HA LVM mode).
(That --non-exclusive option was to map one underlying device to
several mappings on _one_ system, nothing to do with clustered
system.)
Anyway, what is the use case here?
Milan
prev parent reply other threads:[~2011-03-30 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 17:29 [dm-crypt] shared block devices Michael Zabriskie
2011-03-30 21:03 ` Milan Broz [this message]
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=4D939A88.70009@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=mgzabriskie@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