linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Patrik Jonsson <patrik@ucolick.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Strange behaviour on "toy array"
Date: Tue, 17 May 2005 09:41:36 +0100	[thread overview]
Message-ID: <4289AE40.4090201@dgreaves.com> (raw)
In-Reply-To: <42899947.6080107@ucolick.org>

IIRC, Neil submitted a fix for this looping very recently.

yup - 13/May/05 03:55

>Thanks for the ping, things sometimes get lost in the noise....
>
>This sounds a bit like the problem that is addressed by 
>  md-make-raid5-and-raid6-robust-against-failure-during-recovery.patch 
>in the current -mm patches (look in the brokenout directory).
>
>This would only happen if you have multiple failed devices.  So maybe
>while the rebuild was happening, another device failed (which seems to
>happen more and more as device sizes are increasing and reliability is
>going the other way).
>
>Could this (another drive failure) be the case?
>
>NeilBrown
>  
>

I would say that there's been a fair amount of bug fixing activity since
2.6.9 and mdadm 1.6
I'd be happy with them for 'simple' ext3 over md but I'm pretty damned
sure that you'll have problems with xfs and/or lvm2

I _strongly_ suggest 2.6.11.xx and mdadm 1.9 if you'll be playing with
xfs and or lvm2 (which I suggest you do for the system you described)



David



Patrik Jonsson wrote:

> Just as a further comment on what happened when my system hung: The
> process [md0_sync] was rapidly respawning and the syslog filled with
> thousands of messages like these:
>
> May 16 23:16:44 localhost kernel: md: syncing RAID array md0
> May 16 23:16:44 localhost kernel: md: minimum _guaranteed_
> reconstruction speed\
> : 1000 KB/sec/disc.
> May 16 23:16:44 localhost kernel: md: using maximum available idle IO
> bandwith \
> (but not more than 200000 KB/sec) for reconstruction.
> May 16 23:16:44 localhost kernel: md: using 128k window, over a total
> of 960 bl\
> ocks.
> May 16 23:16:44 localhost kernel: md: md0: sync done.
> May 16 23:16:44 localhost kernel: md: syncing RAID array md0
> May 16 23:16:44 localhost kernel: md: minimum _guaranteed_
> reconstruction speed\
> : 1000 KB/sec/disc.
> May 16 23:16:44 localhost kernel: md: using maximum available idle IO
> bandwith \
> (but not more than 200000 KB/sec) for reconstruction.
> May 16 23:16:44 localhost kernel: md: using 128k window, over a total
> of 960 bl\
> ocks.
> May 16 23:16:45 localhost kernel: md: md0: sync done.
> ... etc etc...
>
> I had to halt the system to make it stop. I tried to stop the array
> with mdadm -S /dev/md0 but got "device or resource busy". Did i do
> something illegal here?
>
> Thanks,
>
> /Patrik



  reply	other threads:[~2005-05-17  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050516184049.90DDA11416@smtp.ucolick.org>
2005-05-16 21:54 ` Strange behaviour on "toy array" Patrik Jonsson
2005-05-17  2:28   ` Guy
2005-05-17  6:04     ` Patrik Jonsson
2005-05-17  7:12       ` Patrik Jonsson
2005-05-17  8:41         ` David Greaves [this message]
2005-04-22 10:45 MD bug or me being stupid? Molle Bestefich
2005-05-12  8:55 ` Molle Bestefich
2005-05-13  2:55   ` Neil Brown
2005-05-15 18:10     ` Molle Bestefich
2005-05-15 18:22       ` Strange behaviour on "toy array" Patrik Jonsson
2005-05-15 20:09         ` David Greaves
2005-05-15 20:55           ` Patrik Jonsson
2005-05-15 22:13             ` Guy

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=4289AE40.4090201@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=patrik@ucolick.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).