From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Mattias Wadenstein <maswan@acc.umu.se>,
linux-raid@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: Linux RAID Partition Offset 63 cylinders / 30% performance hit?
Date: Wed, 19 Dec 2007 12:40:55 -0500 [thread overview]
Message-ID: <476957A7.5010805@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712191002580.2468@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Wed, 19 Dec 2007, Mattias Wadenstein wrote:
>
>> On Wed, 19 Dec 2007, Justin Piszcz wrote:
>>
>>> ------
>>>
>>> Now to my setup / question:
>>>
>>> # fdisk -l /dev/sdc
>>>
>>> Disk /dev/sdc: 150.0 GB, 150039945216 bytes
>>> 255 heads, 63 sectors/track, 18241 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0x5667c24a
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/sdc1 1 18241 146520801 fd Linux raid
>>> autodetect
>>>
>>> ---
>>>
>>> If I use 10-disk RAID5 with 1024 KiB stripe, what would be the
>>> correct start and end size if I wanted to make sure the RAID5 was
>>> stripe aligned?
>>>
>>> Or is there a better way to do this, does parted handle this
>>> situation better?
>>
>>> From that setup it seems simple, scrap the partition table and use the
>> disk device for raid. This is what we do for all data storage disks
>> (hw raid) and sw raid members.
>>
>> /Mattias Wadenstein
>>
>
> Is there any downside to doing that? I remember when I had to take my
> machine apart for a BIOS downgrade when I plugged in the sata devices
> again I did not plug them back in the same order, everything worked of
> course but when I ran LILO it said it was not part of the RAID set,
> because /dev/sda had become /dev/sdg and overwrote the MBR on the
> disk, if I had not used partitions here, I'd have lost (or more of the
> drives) due to a bad LILO run?
As other posts have detailed, putting the partition on a 64k aligned
boundary can address the performance problems. However, a poor choice of
chunk size, cache_buffer size, or just random i/o in small sizes can eat
up a lot of the benefit.
I don't think you need to give up your partitions to get the benefit of
alignment.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2007-12-19 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 14:50 Linux RAID Partition Offset 63 cylinders / 30% performance hit? Justin Piszcz
2007-12-19 15:01 ` Mattias Wadenstein
2007-12-19 15:04 ` Justin Piszcz
2007-12-19 15:06 ` Jon Nelson
2007-12-19 15:31 ` Justin Piszcz
2007-12-20 10:37 ` Gabor Gombas
2007-12-19 17:40 ` Bill Davidsen [this message]
2007-12-19 17:37 ` Jon Nelson
2007-12-19 17:37 ` Jon Nelson
2007-12-19 17:55 ` Justin Piszcz
2007-12-19 19:18 ` Bill Davidsen
2007-12-19 19:44 ` Justin Piszcz
2007-12-19 21:31 ` Justin Piszcz
2007-12-20 15:18 ` Bill Davidsen
2007-12-20 15:00 ` Justin Piszcz
2007-12-20 10:24 ` Gabor Gombas
2007-12-20 10:33 ` Gabor Gombas
2007-12-19 21:44 ` Michal Soltys
2007-12-19 22:12 ` Jon Nelson
2007-12-20 13:01 ` Michal Soltys
2007-12-19 21:59 ` Robin Hill
2007-12-19 22:03 ` Justin Piszcz
2007-12-25 19:06 ` Bill Davidsen
2007-12-29 17:22 ` dean gaudet
2007-12-29 17:34 ` Justin Piszcz
2007-12-30 1:33 ` Michael Tokarev
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=476957A7.5010805@tmr.com \
--to=davidsen@tmr.com \
--cc=apiszcz@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=maswan@acc.umu.se \
/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).