All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico <undicizeri@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID1 extreme low performance
Date: Fri, 12 Dec 2008 13:47:31 +0100	[thread overview]
Message-ID: <26c008d70812120447kb91f8a1x6747bf5d4c7cfc0c@mail.gmail.com> (raw)

I all,
a couple of weeks ago I've updated the kernel (now I'm using .27-7)
and mdadm to version 2.6.7 and now I have terrible RAID1 performance:
during I/O operation I have 100% cpu utilization and all the system
freeze until the operation ends. Seeking and reading from the RAID is
extremely slow (sometime 4 or 5 seconds just to show an "ls -l"
output) and writing is even worst.
I've tested the same hard disk without RAID and It seem working well.
This is the output of mdadm -D /dev/md*


/dev/md0:
        Version : 00.90
  Creation Time : Sat May  3 21:53:16 2008
     Raid Level : raid1
     Array Size : 7815488 (7.45 GiB 8.00 GB)
  Used Dev Size : 7815488 (7.45 GiB 8.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Dec 12 13:46:27 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 2a37b0a1:4b6b28fc:0209446b:c3b28f2a
         Events : 0.142

    Number   Major   Minor   RaidDevice State
       0       8       37        0      active sync   /dev/sdc5
       1       8       17        1      active sync   /dev/sdb1

/dev/md1:
        Version : 00.90
  Creation Time : Sat May  3 21:53:32 2008
     Raid Level : raid1
     Array Size : 152264000 (145.21 GiB 155.92 GB)
  Used Dev Size : 152264000 (145.21 GiB 155.92 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Fri Dec 12 13:46:27 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 19c49c5d:e3193aa1:657f267b:b23c2dee
         Events : 0.14

    Number   Major   Minor   RaidDevice State
       0       8       38        0      active sync   /dev/sdc6
       1       8       18        1      active sync   /dev/sdb2

/dev/md2:
        Version : 00.90
  Creation Time : Mon May  5 03:39:59 2008
     Raid Level : raid1
     Array Size : 293049600 (279.47 GiB 300.08 GB)
  Used Dev Size : 293049600 (279.47 GiB 300.08 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Fri Dec 12 13:37:06 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 62a5cb51:36ca61a3:1298e6c2:30fde3ba
         Events : 0.20

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       33        1      active sync   /dev/sdc1

             reply	other threads:[~2008-12-12 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 12:47 Federico [this message]
2008-12-16  2:35 ` RAID1 extreme low performance Neil Brown

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=26c008d70812120447kb91f8a1x6747bf5d4c7cfc0c@mail.gmail.com \
    --to=undicizeri@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.