From: Milan Broz <mbroz@redhat.com>
To: "Karl O. Pinc" <kop@meme.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] (More) Questions about LUKS / LVM
Date: Tue, 20 Sep 2011 20:19:54 +0200 [thread overview]
Message-ID: <4E78D94A.2080800@redhat.com> (raw)
In-Reply-To: <1316542007.4663.0@mofo>
On 09/20/2011 08:06 PM, Karl O. Pinc wrote:
> Performance is also going to suck if you don't get
> alignment right on drives with 4Kb sectors.
Data area for LUKS was always aligned to 4k offset, so
you should never see problem here.
(Underlying disk partitioning is another issue of course.)
>
> FWIW here are the links I use to deal with 4Kb sector issues.
>
> http://ata.wiki.kernel.org/index.php/ATA_4_KiB_sector_issues
(down, for the same reason like all kernel.org services...)
> http://lists.debian.org/debian-user/2011/01/msg02021.html
Not completely up to date. Almost all tools actively use topology
information (from kernel) or default to 1MiB alignment.
(fdisk, parted, lvm, cryptsetup, mdadm, etc)
I would say - if you are using recent distro, you have aligned
this correctly by default (when creating new storage stack).
Do not try to use any magic options, only do this if you are
sure that default result is wrong.
(And report bug if you see it with new versions of tools,
storage people spent a lot of time fixing to work it correctly.)
Milan
next prev parent reply other threads:[~2011-09-20 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 10:36 [dm-crypt] (More) Questions about LUKS / LVM Robbie Smith
2011-09-20 10:52 ` Quentin Lefebvre
2011-09-20 11:47 ` Arno Wagner
2011-09-20 13:13 ` Milan Broz
2011-09-20 14:14 ` Arno Wagner
2011-09-20 14:52 ` Milan Broz
2011-10-03 6:17 ` Luca Berra
2011-10-03 10:55 ` Arno Wagner
2011-09-20 15:21 ` Alexander Koch
2011-09-20 16:12 ` Milan Broz
2011-09-20 17:41 ` Arno Wagner
2011-09-20 18:06 ` Karl O. Pinc
2011-09-20 18:19 ` Milan Broz [this message]
2011-09-21 10:22 ` Arno Wagner
2011-09-21 16:14 ` Dragan Milivojevic
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=4E78D94A.2080800@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=kop@meme.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 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.