From: Michael Evans <mjevans1983@gmail.com>
To: Khelben Blackstaff <eye.of.the.8eholder@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Alignment of RAID on specific boundary
Date: Mon, 4 Jan 2010 22:57:48 -0800 [thread overview]
Message-ID: <4877c76c1001042257h49103054t977de11410eb65c6@mail.gmail.com> (raw)
In-Reply-To: <7b3edae11001041130n42d053fcpc4923b22278c5671@mail.gmail.com>
On Mon, Jan 4, 2010 at 11:30 AM, Khelben Blackstaff
<eye.of.the.8eholder@gmail.com> wrote:
He's using SDDs with 128KByte erase blocks.
> Is there a way to make the RAID data start at a particular offset ?
> (In my case 512 sectors) ?
>
> Thank you for your time.
> --
You want the RAID data chunks aligned so that they start on a 512byte
sector address that fulfills (sector & 0xFF) == 0.
As far as I am aware, using metadata 0.90 OR 1.0 will start the actual
data at the beginning of the partition, reserve some space near the
end, and use the very end for the metadata.
Format 1.1 will reserve the space at the beginning, and I have just checked;
00000400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00003000 (LVM2 header)
It starts the LVM2 header after 0x3000 bytes (64K chunk size); I'd
hope to see it around 0x10000.
It looks like the data isn't padded up to the desired offset.
I agree, it would be useful to have an option to specify the offset of
the first data chunk.
next prev parent reply other threads:[~2010-01-05 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 19:30 Alignment of RAID on specific boundary Khelben Blackstaff
2010-01-04 21:14 ` David Rees
2010-01-04 21:51 ` Khelben Blackstaff
2010-01-05 8:24 ` Antonio Perez
2010-01-05 13:02 ` Khelben Blackstaff
2010-01-05 6:57 ` Michael Evans [this message]
2010-01-05 7:50 ` Michal Soltys
2010-01-05 13:44 ` Khelben Blackstaff
2010-01-05 15:35 ` John Robinson
2010-01-06 1:46 ` Michael Evans
[not found] ` <7b3edae11001060500g2d63f2cav81bf8a90fc0b946b@mail.gmail.com>
2010-01-06 14:44 ` Khelben Blackstaff
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=4877c76c1001042257h49103054t977de11410eb65c6@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=eye.of.the.8eholder@gmail.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).