From: Stan Hoeppner <stan@hardwarefreak.com>
To: Pol Hallen <raid1@fuckaround.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: standard performance (write speed ??Mb/s) - new raid5 array
Date: Thu, 21 Jul 2011 19:05:23 -0500 [thread overview]
Message-ID: <4E28BEC3.4000301@hardwarefreak.com> (raw)
In-Reply-To: <201107211907.36864.raid1@fuckaround.org>
On 7/21/2011 12:07 PM, Pol Hallen wrote:
> Hello again :-)
>
> I removed all partitions of my disks and do:
>
> dd if=/dev/zero of=/dev/sdb bs=512 count=1 for all disks..
>
> next, I created a new partition (non-fs data) starting of 64 like below (for
> every devices)
Why did you create partitions? The whole point of zeroing the first 512
bytes was to *eliminate* all the partitions...
> Device Boot Start End Blocks Id System
> /dev/sdb1 64 3907029167 1953514552 da Non-FS data
>
> created a new raid5 array:
>
> mdadm --create --verbose /dev/md0 --level=raid5 --raid-devices=5 /dev/sdb
> /dev/sdc /dev/sdd /dev/sde /dev/sdf
And now you create your array without using partitions...
> cat /proc/mdstat
>
> md0 : active raid5 sdf[5] sde[3] sdd[2] sdc[1] sdb[0]
> 7814051840 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4]
> [UUUU_]
> [>....................] recovery = 0.3% (6625324/1953512960)
> finish=971.1min speed=33411K/sec
You created aligned partitions on all disks, and then did not use those
partitions...
> Now, I've 5 identical disks (2Tb WD)
>
> I've to wait rebuilding time after do new tests performance.
>
> The procedure that I've done is correct?
No, you did not. It seems you merged bits and pieces from each array
creation method. The array may still function properly. I've never
tried what you've done here. Maybe others have the correct answer.
--
Stan
next prev parent reply other threads:[~2011-07-22 0:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 19:40 standard performance (write speed 20Mb/s) Pol Hallen
2011-07-17 4:26 ` Stan Hoeppner
2011-07-17 8:12 ` Pol Hallen
2011-07-17 12:11 ` John Robinson
2011-07-17 12:22 ` Iustin Pop
2011-07-17 12:51 ` John Robinson
2011-07-17 13:28 ` Iustin Pop
2011-07-18 9:04 ` John Robinson
2011-07-17 22:05 ` Stan Hoeppner
2011-07-27 5:42 ` Simon Matthews
2011-07-27 5:46 ` Roman Mamedov
2011-07-27 10:22 ` Stan Hoeppner
2011-07-27 10:26 ` John Robinson
2011-07-27 12:35 ` Joe Landman
2011-07-27 13:54 ` Stan Hoeppner
2011-07-17 23:03 ` Stan Hoeppner
2011-07-18 11:52 ` Pol Hallen
2011-07-21 17:07 ` standard performance (write speed ??Mb/s) - new raid5 array Pol Hallen
2011-07-22 0:05 ` Stan Hoeppner [this message]
2011-07-22 7:08 ` Pol Hallen
2011-07-22 8:13 ` Erwan Leroux
2011-07-17 16:48 ` standard performance (write speed 20Mb/s) Gordon Henderson
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=4E28BEC3.4000301@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=raid1@fuckaround.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).