From: Marc MERLIN <marc@merlins.org>
To: john terragon <jterragon@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs on software RAID0
Date: Wed, 7 May 2014 02:01:01 -0700 [thread overview]
Message-ID: <20140507090101.GC19238@merlins.org> (raw)
In-Reply-To: <CANg_oxw_qy154eiRw9zdsCUwR1JTOGsUEa=VWq-7RM=nsATU3g@mail.gmail.com>
On Tue, May 06, 2014 at 09:02:46AM +0200, john terragon wrote:
> just one last doubt:
>
> why do you use --align-payload=1024? (or 8912)
> Cryptsetup man says that the default for the payload alignment is 2048
> (512-byte sectors). So, it's already aligned by default to 4K-byte
> physical sectors (if that was your concern). Am I missing something?
With 4K sectors, I agree that 2048 would be better.
What I was trying to do there is avoid write amplification.
After reading
http://wiki.drewhess.com/wiki/Creating_an_encrypted_filesystem_on_a_partition
I went with
mdadm --create /dev/md8 --level=5 --raid-devices=5 /dev/sd[abdef]1 --chunk=256 --bitmap=/boot/bitmap-md8
which I believe required me to use
cryptsetup luksFormat --align-payload=1024 -s 256 -c aes-xts-plain64 /dev/md8
(that was with 5 drives, or 4 drives with data).
Would agree with the math?
If so, for 4K sector sizes, if we have to use align-payload=1024, in
turn I'd have to use --chunk=512.
Does that sound right?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
prev parent reply other threads:[~2014-05-07 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 20:51 btrfs on software RAID0 john terragon
2014-05-05 21:25 ` Marc MERLIN
2014-05-05 21:42 ` ronnie sahlberg
2014-05-05 22:06 ` Marc MERLIN
2014-05-05 22:21 ` john terragon
2014-05-06 7:02 ` john terragon
2014-05-07 9:01 ` Marc MERLIN [this message]
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=20140507090101.GC19238@merlins.org \
--to=marc@merlins.org \
--cc=jterragon@gmail.com \
--cc=linux-btrfs@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 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.