From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: RAID partition starting sector (... 63?)
Date: Wed, 17 Feb 2010 15:13:46 +0000 [thread overview]
Message-ID: <73e903671002170713g397742b8l109773b4c20825ce@mail.gmail.com> (raw)
Hi,
I remember seeing some discussion on what sector a partition starts
on. Many programs create partitions that start on sector 63, which
doesn't really make any intuitive sense to me. I just lost a disk from
of a RAID10 array and was thinking I'd try to understand this issue as
I have to do some disk/block/partition wrangling anyway.
From a discussion from linux-raid titled "Raid 10 LVM JFS Seeking
performance help", I found the following:
On Mon, Dec 21, 2009 at 12:56 PM, Goswin von Brederlow
<goswin-v-b@web.de> wrote:
>
> Also, on a lower level, make sure your raid does not start on a
> partition starting at sector 63 (which is still the default in many
> partitioning progs). That easily results in bad alignment causing 4k
> chunks to land on 2 sectors. But you need to test that with your
> specific drive to see if it really is a problem.
>
Hmm ... In short: Do I want to have a partition start on any
particular sector? Especially in the case where I want to ...
- build a RAID10 with partitions (i.e. not with raw devices)
- using ~256K chunks
- and have a nice JFS filesystem on top of it.
Starting on sector 64 feels conceptually "prettier" than Sector 63,
but I can't picture the case where it behaves any different. Except
perhaps when GRUB expects stuff to begin at sector 63, making a mess
if we're starting at sector 64. Though it *should* work OK, of course.
Anyways ... Any tips on a subtle matter most well appreciated.
Especially tell me if I'm overthinking, please. Thanks.
-- Kristleifur
next reply other threads:[~2010-02-17 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 15:13 Kristleifur Daðason [this message]
2010-02-17 15:18 ` RAID partition starting sector (... 63?) Mikael Abrahamsson
2010-02-17 15:23 ` Martin K. Petersen
2010-02-17 16:15 ` Goswin von Brederlow
2010-02-17 16:24 ` Martin K. Petersen
2010-02-17 18:13 ` Greg Freemyer
2010-02-17 18:42 ` Martin K. Petersen
2010-02-17 15:25 ` Greg Freemyer
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=73e903671002170713g397742b8l109773b4c20825ce@mail.gmail.com \
--to=kristleifur@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).