From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Wrong behavior?
Date: Wed, 14 Jul 2010 14:13:46 +0200 [thread overview]
Message-ID: <20100714121346.GA19846@tansi.org> (raw)
In-Reply-To: <1279109239.2415.10.camel@Koma-Station.localdomain>
The LUKS header is 1'052'672 bytes with default parameters.
See FAQ Item "What does the on-disk structure of LUKS look like?"
in section 5.
Arno
On Wed, Jul 14, 2010 at 02:07:19PM +0200, Sven Eschenberg wrote:
> Hi Milan,
>
> thanks for the info and links. What I do not understand is this, I will
> use the easiest version for now:
>
> cryptsetup luksFormat /dev/md125
>
> And:
>
> LUKS header information for /dev/md125
>
> Version: 1
> Cipher name: aes
> Cipher mode: cbc-essiv:sha256
> Hash spec: sha1
> Payload offset: 4096
>
> But:
>
> cat /sys/block/md125/queue/minimum_io_size
> 524288
>
> cat /sys/block/md125/queue/optimal_io_size
> 1048576
>
> whilst physical and logical blocksize are at 512 bytes.
>
> I don't see why cryptsetup does not end up with 1024 sectors (which is
> the optimal_io_size) - or is the luks header bigger than 512k? even
> bigger than 1 MB (2048 sectors) ?
>
> Regards
>
> -Sven
>
>
>
>
> On Wed, 2010-07-14 at 13:52 +0200, Milan Broz wrote:
> > On 07/14/2010 01:39 PM, Sven Eschenberg wrote:
> >
> > > Is there any 'easy' way to access this information. specifically I am
> > > interested, why md would report a 6144 sectors alignment on my 4 disk
> > > raid5 with 512 kb chunks instead of 3072.
> >
> > Values are in in sysfs also, I am just using topology ioctl which is simpler.
> >
> > sysfs interface
> > ---------------
> > /sys/block/<disk>/alignment_offset
> > /sys/block/<disk>/<partition>/alignment_offset
> > /sys/block/<disk>/queue/physical_block_size
> > /sys/block/<disk>/queue/logical_block_size
> > /sys/block/<disk>/queue/minimum_io_size
> > /sys/block/<disk>/queue/optimal_io_size
> >
> > cryptsetup uses minimal/optimal io_size and alignment value
> > to calculate payload offset.
> >
> > A lot of info here:
> >
> > http://people.redhat.com/msnitzer/docs/io-limits.txt
> > https://ata.wiki.kernel.org/index.php/ATA_4_KiB_sector_issues
> >
> > Milan
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-07-14 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:51 [dm-crypt] Wrong behavior? Sven Eschenberg
2010-07-13 21:12 ` Milan Broz
2010-07-13 22:17 ` Sven Eschenberg
[not found] ` <AANLkTilvdewwcdzdm2uX6go9q2dahLX7Fes-lwDNOkvU@mail.gmail.com>
2010-07-14 6:07 ` MkFly
2010-07-14 6:38 ` Heinz Diehl
2010-07-14 8:20 ` Milan Broz
2010-07-14 10:09 ` Arno Wagner
2010-07-14 18:09 ` Christoph Anton Mitterer
2010-07-14 7:58 ` Milan Broz
2010-07-14 11:39 ` Sven Eschenberg
2010-07-14 11:52 ` Milan Broz
2010-07-14 12:07 ` Sven Eschenberg
2010-07-14 12:13 ` Arno Wagner [this message]
2010-07-14 12:53 ` Milan Broz
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=20100714121346.GA19846@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.