All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Phantazm" <phantazm@phantazm.nu>
To: linux-raid@vger.kernel.org
Subject: Huge mdadm resync problem.
Date: Thu, 17 Feb 2005 13:08:01 +0100	[thread overview]
Message-ID: <cv219o$ose$1@sea.gmane.org> (raw)

This is really wierd problem with mdadm.

I currently have 8 Maxtor 200gb disks.
They are connected like this

hdb hdc hdd = onboard ide
hde hdf hdg hdh = Promise ata133 card
hdk = Promise ata 133 card.

Hardware is a P4 2.8ghz with 2gb of ram and a MSI NEO 2 mobo.

Problem is that te resync is really slow and when it's done it just loops 
and the box craches.
Here are some info.

Currently i'm testing a resync with a non HT/SMP config and noapic just to 
check that is no irq routing crap. (failed before though)

merlin / # uname -a
Linux merlin 2.6.10-gentoo-r6 #16 Thu Feb 17 11:00:11 CET 2005 i686 Intel(R) 
Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux


merlin / # cat /proc/interrupts
           CPU0
  0:    6621371          XT-PIC  timer
  1:          8          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  3:    1487791          XT-PIC  eth1
 10:    1628242          XT-PIC  eth0, eth2
 11:     112644          XT-PIC  ide2, ide3
 12:      35197          XT-PIC  ide5
 14:      71092          XT-PIC  ide0
 15:      63376          XT-PIC  ide1
NMI:          0
ERR:      40328

cat /proc/mdstat
Personalities : [raid5]
md0 : active raid5 hde1[0] hdb1[8] hdd1[7] hdk1[6] hdc1[4] hdh1[3] hdg1[2] 
hdf1[1]
      1393991424 blocks level 5, 64k chunk, algorithm 2 [8/7] [UUUUU_UU]
      [=>...................]  recovery =  5.5% (11110168/199141632) 
finish=1641.7min speed=1906K/sec
unused devices: <none>

(The resync speed is always somewhere between 500K to 3000K/s) should be 
10000K/s  ;-)


This is the kernelog. it's just a lil grab in it since this list goes on 
untill i reboot the box. (its freezed).
This is what i get when sync is finiched and it should markt the array good.
Feb 17 07:17:08 [kernel] md: using maximum available idle IO bandwith (but 
not more than 150000 KB/sec) for reconstruction.
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: using maximum available idle IO bandwith (but 
not more than 150000 KB/sec) for reconstruction.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0
Feb 17 07:17:08 [kernel] md: md0: sync done.
Feb 17 07:17:08 [kernel] .<6>md: syncing RAID array md0

I've also tried to have 4 disks on each promise card with same result. (if 
having apic i get alot of cpu apic error 60)
i have checked all disks with smarttool and also benchmarked them. Each disk 
gets about (hdparm) -T = 1800mb/s and -t 60mb/s so i doubt that
theres actually a broken disk.

i'm running mdadm 1.7.0

This is toally bugging me out.
Help is really really apricated. 




             reply	other threads:[~2005-02-17 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 12:08 Phantazm [this message]
2005-02-17 12:37 ` Huge mdadm resync problem Phantazm
  -- strict thread matches above, loose matches on Subject: below --
2005-02-17 13:52 Lord Hess,Raum 301Kw,54-8994
2005-02-17 14:33 ` Phantazm
2005-02-17 14:40   ` Gordon Henderson
2005-02-17 14:57     ` Phantazm

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='cv219o$ose$1@sea.gmane.org' \
    --to=phantazm@phantazm.nu \
    --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.