From: Coly Li <colyli@suse.de>
To: Jorg Bornschein <jb@capsec.org>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Can't register existing backing devices anymore
Date: Sun, 13 Aug 2017 23:40:47 +0800 [thread overview]
Message-ID: <939a4d7b-add7-08d6-a68d-24c4dc8bd7e7@suse.de> (raw)
In-Reply-To: <a2cb2667df612d0509f2c60e47ff67c5@889215b17b02>
On 2017/8/13 下午11:40, Jorg Bornschein wrote:
> August 13, 2017 4:27 PM, "Coly Li" <colyli@suse.de> wrote:
>
> Hi Coly,
>
>> Could you please give me some hint how the /dev/dm- nodes are created ?
>> I will try to reproduce it on my hardware.
>>
>> Thanks for the report.
>
> I created them with 'cryptsetup luksFormat ...', IIRC. When I run 'cryptsetup luksDump' I get:
>
> Version: 1
> Cipher name: aes
> Cipher mode: xts-plain64
> Hash spec: sha256
> Payload offset: 4096
> MK bits: 256
> MK digest: <STUFF>
> MK salt: <STUFF>
> MK iterations: 400000
> UUID: 81a8d12e-9309-4317-b447-ab3c86e2f7ea
>
> Key Slot 0: ENABLED
> Iterations: 3200000
> Salt: <STUFF>
> Key material offset: 8
> AF stripes: 4000
>
>
> and this is the contents of my /etc/crypttab:
>
> # <name> <device> <password> <options>
> crypted-sdb /dev/sdb1 /etc/cryptfs.key
> crypted-sdc /dev/sdc1 /etc/cryptfs.key
> crypted-sdd /dev/sdd1 /etc/cryptfs.key
> crypted-sde /dev/sde1 /etc/cryptfs.key
Oh, I don't use cryptsetup before, let me try ... Thanks for the hint :-)
Coly Li
next prev parent reply other threads:[~2017-08-13 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 12:22 Can't register existing backing devices anymore Jorg Bornschein
2017-08-13 15:23 ` Coly Li
2017-08-13 15:40 ` Jorg Bornschein
2017-08-13 15:40 ` Coly Li [this message]
2017-08-13 17:20 ` Jorg Bornschein
2017-08-14 17:17 ` Jorg Bornschein
2017-08-24 0:44 ` Eric Wheeler
2017-08-24 16:44 ` Coly Li
2017-08-24 20:36 ` Eric Wheeler
2017-08-24 21:02 ` Jorg Bornschein
2017-10-27 19:38 ` Eric Wheeler
2017-10-27 19:41 ` Michael Lyle
2017-10-27 21:14 ` Eric Wheeler
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=939a4d7b-add7-08d6-a68d-24c4dc8bd7e7@suse.de \
--to=colyli@suse.de \
--cc=jb@capsec.org \
--cc=linux-bcache@vger.kernel.org \
/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