All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Rosemann <heiko.rosemann@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] change passphrase
Date: Tue, 01 Apr 2014 23:21:31 +0200	[thread overview]
Message-ID: <533B2DDB.3020307@web.de> (raw)
In-Reply-To: <1396378962.7061.101552289.658497F8@webmail.messagingengine.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/01/2014 09:02 PM, Biltong wrote:
> I have a raid-1 system running btrfs on top of luks.
> 
> I cannot remember my passphrase, but the system is running and I
> have made a backup.
> 
> I'd like to add a new passphrase, and have followed the
> instructions from 6.10 at
> 
http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Backup_and_Data_Recovery
> 
> This worked for the first device, which seems to work with
> /dev/dm-0, but I cannot work out what the device name for the
> second raid-1 member is. The btrfs partition is on top of the luks
> device, and so I need to change both.
> 

I'm not really clear on what your setup is, but there's basically two
choices:

1) encrypt 2 partitions separately (typically /dev/sdxy with x in a..z
and y in
1..) leading to /dev/mapper/a and /dev/mapper/b as links to /dev/dm-0
and /dev/dm-1
2) create RAID1 from /dev/mapper/a and /dev/mapper/b, causing /dev/md0
to appear
3) create btrfs (or whatever) on top of /dev/md0

or

1) create RAID1 from 2 partitions (typically /dev/sdxy as above) leading
to /dev/md0
2) encrypt /dev/md0 leading to /dev/mapper/a as a link to /dev/dm-0
3) create btrfs (or whatever) on top of /dev/dm-0


If you can't find /dev/dm-1, you might be using the second version. You
can also find some information in the output of the mount command (which
should show you the crypto device in the first and the RAID device in
the second scenario) and from /proc/mdstat showing /dev/mapper/a (or
/dev/dm-0) in the first and /dev/sdxy in the second case.

Good luck with the research,
Heiko

- -- 
eMails verschlüsseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlM7LdQACgkQ/Vb5NagElAVK2gCgq7EVxGcc3sTlIgEF3M4oZH62
LrQAn3kmHpBRcnjbWCbBsug5tQYKWS/s
=lSG+
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-04-01 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 19:02 [dm-crypt] change passphrase Biltong
2014-04-01 21:21 ` Heiko Rosemann [this message]
2014-04-02  9:41   ` Sven Eschenberg

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=533B2DDB.3020307@web.de \
    --to=heiko.rosemann@web.de \
    --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.