linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolae Mihalache <mache@abcpages.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: slow sequential read on partitioned raid6
Date: Wed, 17 Mar 2010 00:16:29 +0100	[thread overview]
Message-ID: <4BA0114D.9050405@abcpages.com> (raw)
In-Reply-To: <20100317092219.35393819@notabene.brown>

On 03/16/2010 11:22 PM, Neil Brown wrote:
> On Tue, 16 Mar 2010 20:05:45 +0100
> Nicolae Mihalache <mache@abcpages.com> wrote:
>   
>> Hello,
>>
>> I have created a partitioned raid6 array over 6x1TB SATA disks using the
>> command (from memory): mdadm --create --auto=mdp --level=6
>> --raid-devices /dev/md_d1 /dev/sd[b-g].
>>
>> When I run a sequential read test using
>> dd if=/dev/md_d1p1 of=/dev/null bs=1M
>> I get low read speeds of around 80MB/s but only when the partition is
>> mounted.
>>
>> If I unmount, the speed is around 350MB/s. The filesystems I tried are
>> ext3 and xfs.
>>     
>
> Thanks for reporting this.
>
> I just did some testing and I get the reverse!!
>
> When a filesystem is mounted I get 135MB/s.  When it isn't mounted
> I get 64MB/s.
>
> I cannot think what could cause this.  I will have to explore.
> Can you please double check you results and confirm that it definitely
> is  faster then unmounted.
>   
I'm positive that it's slow when mounted, that's how I discovered the
problem. See below (I recreated the array over 1/10 of the original
disks to be able to test easier).
In fact the highest speed I get when accessing directly the entire disk
even when one partition is mounted.


bacula:~# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md_d1 : active raid6 sdg1[5] sdf1[4] sde1[3] sdd1[2] sdc1[1] sdb1[0]
      390668288 blocks level 6, 64k chunk, algorithm 2 [6/6] [UUUUUU]

md2 : active raid1 sdi1[0] sdj1[1]
      1462750272 blocks [2/2] [UU]

unused devices: <none>

bacula:~# parted  /dev/md_d1
GNU Parted 1.8.8
Using /dev/md_d1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: Unknown (unknown)
Disk /dev/md_d1: 400GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 1      17.4kB  50.0GB  50.0GB  ext3         primary

(parted) quit

bacula:~# umount /dev/md_d1p1
umount: /dev/md_d1p1: not mounted

bacula:~# dd if=/dev/md_d1p1 of=/dev/null bs=1M count=10000
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB) copied, 37.4938 s, 280 MB/s

bacula:~# mount /dev/md_d1p1 /mnt

bacula:~# dd if=/dev/md_d1p1 of=/dev/null bs=1M count=10000
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB) copied, 132.894 s, 78.9 MB/s

bacula:~# dd if=/dev/md_d1 of=/dev/null bs=1M count=10000
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB) copied, 28.222 s, 372 MB/s

  reply	other threads:[~2010-03-16 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 19:05 slow sequential read on partitioned raid6 Nicolae Mihalache
2010-03-16 22:22 ` Neil Brown
2010-03-16 23:16   ` Nicolae Mihalache [this message]
     [not found]     ` <1268783497.3781.14.camel@localhost.localdomain>
2010-03-17  8:23       ` Nicolae Mihalache
2010-03-18  2:40         ` Michael Evans
2010-03-19  6:47           ` Nicolae Mihalache
2010-03-19  8:16             ` Michael Evans

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=4BA0114D.9050405@abcpages.com \
    --to=mache@abcpages.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).