From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup luksFormat with the size option
Date: Sun, 2 Feb 2014 01:18:19 +0100 [thread overview]
Message-ID: <20140202001819.GA8664@tansi.org> (raw)
In-Reply-To: <lck07r$93q$1@ger.gmane.org>
On Sun, Feb 02, 2014 at 00:33:27 CET, Robert Nichols wrote:
> On 02/01/2014 03:34 PM, Arno Wagner wrote:
> >On Sat, Feb 01, 2014 at 21:50:19 CET, Matthew Thode wrote:
> >>Am I correct in stating that setting --size=8 will make the sectors 4k
> >>in size? Also, how can I check what existing luks volumes are set to?
> >>
> >>--
> >>-- Matthew Thode
> >>
> >
> >No, you are not. As the man-page clearly states, this sets the
> >size of the underlying device as multiple of 512B sectors.
>
> I submit that for the luksFormat action, the --size option does _nothing_!
Yes. Nor should it. See the man-page:
--size, -b <number of 512 byte sectors>
Force the size of the underlying device in sectors of 512 bytes.
This option is only relevant for the open and resize actions.
^^^^ ^^^^^^
I do not see why this is apparently a surprise to some....
> The size is not recorded in the LUKS header, and luksFormat does not open
> the encrypted device, so there is neither a temporary nor a persistent
> effect from that option. In fact, there is not even a check that the
> requested size is within the limits of the underlying device.
And why should there be? The underlying device could change.
Or the kernel could change and with it the limits. Really,
this is KISS at work. Watch and learn.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
next prev parent reply other threads:[~2014-02-02 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 20:50 [dm-crypt] cryptsetup luksFormat with the size option Matthew Thode
2014-02-01 21:34 ` Arno Wagner
2014-02-01 23:33 ` Robert Nichols
2014-02-02 0:18 ` Arno Wagner [this message]
2014-02-02 0:35 ` Robert Nichols
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=20140202001819.GA8664@tansi.org \
--to=arno@wagner.name \
--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.