linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Molle Bestefich <molle.bestefich@gmail.com>
To: linux-raid@vger.kernel.org
Cc: neilb@cse.unsw.edu.au
Subject: Re: MD bug or me being stupid?
Date: Thu, 12 May 2005 10:55:30 +0200	[thread overview]
Message-ID: <62b0912f050512015585a6ba5@mail.gmail.com> (raw)
In-Reply-To: <62b0912f0504220345349335f9@mail.gmail.com>

On 4/22/05, Molle Bestefich wrote:
> Just upgraded a MD RAID 5 box to 2.6.11 from 2.4.something.
> 
> Found out one disk was failing completely, got a replacement from Maxtor.  Neat.
> Replaced disk, rebooted..
> Added the new disk to the array with 'raidhotadd'.
> MD started syncing.
> 
> A couple of minutes into the process, it started *seriously* spamming
> the console with messages:
> 
> ==========================
> Apr 22 01:47:00 linux kernel: ..<6>md: syncing RAID array md1
> Apr 22 01:47:00 linux kernel: md: minimum _guaranteed_ reconstruction
> speed: 1000 KB/sec/disc.
> Apr 22 01:47:00 linux kernel: md: using maximum available idle IO bandwith (but
> not more than 200000 KB/sec) for reconstruction.
> Apr 22 01:47:00 linux kernel: md: using 128k window, over a total of
> 199141632 blocks.
> Apr 22 01:47:00 linux kernel: md: md1: sync done.
> Apr 22 01:47:00 linux kernel: ..<6>md: syncing RAID array md1
> Apr 22 01:47:01 linux kernel: md: minimum _guaranteed_ reconstruction
> speed: 1000 KB/sec/disc.
> Apr 22 01:47:01 linux kernel: md: using maximum available idle IO bandwith (but
> not more than 200000 KB/sec) for reconstruction.
> Apr 22 01:47:01 linux kernel: md: using 128k window, over a total of
> 199141632 blocks.
> Apr 22 01:47:01 linux kernel: md: md1: sync done.
> ==========================

[snip]

> afterwards, I can see that the above messages repeat themselves.
> cat /var/log/messages | grep md | grep 'Apr 22 01:47:01' | grep 'sync done'
> tells me that the messages were repeated 12 times per second.  The

Ping!...
Neil, just wondering, any comments regarding this particular endless loop in MD?
(Anything I can test or some such?)

  parent reply	other threads:[~2005-05-12  8:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 10:45 MD bug or me being stupid? Molle Bestefich
2005-04-22 11:25 ` Molle Bestefich
2005-05-12  8:55 ` Molle Bestefich [this message]
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=62b0912f050512015585a6ba5@mail.gmail.com \
    --to=molle.bestefich@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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).