linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Molle Bestefich <molle.bestefich@gmail.com>
To: Phantazm <phantazm@phantazm.nu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Bug in MDADM or just crappy computer?
Date: Fri, 22 Apr 2005 14:26:06 +0200	[thread overview]
Message-ID: <62b0912f050422052612fac70a@mail.gmail.com> (raw)
In-Reply-To: <cv9gbc$84g$1@sea.gmane.org>

Phantazm wrote:
> And the kernel log is filled up with this.
> 
> Feb 20 08:43:13 [kernel] md: md0: sync done.
> Feb 20 08:43:13 [kernel] md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.
> Feb 20 08:43:13 [kernel] md: md0: sync done.
> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

No "sync done" here? What is it doing, multiple syncs in parallel?

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

Again (below line)?

> Feb 20 08:43:13 [kernel] md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.
> Feb 20 08:43:13 [kernel] md: using maximum available idle IO bandwith (but
> not more than 15000 KB/sec) for reconstruction.
> Feb 20 08:43:13 [kernel] md: using 128k window, over a total of 199141632
> blocks.
> Feb 20 08:43:13 [kernel] md: md0: sync done.

There we go, a "sync done" (above)....

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

But then again (below)..

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

And again...

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

And again...

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

And again?!

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

And again...

> Feb 20 08:43:13 [kernel] .<6>md: syncing RAID array md0
> Feb 20 08:43:13 [kernel] md: minimum _guaranteed_ reconstruction speed: 5000
> KB/sec/disc.

And again...

> Feb 20 08:43:13 [kernel] md: syncing RAID array md0

[snip]
Odd!

> aint got a single clue what it could be.

I'm seeing something that looks like the same, so let me know if you
found out what happened.

      parent reply	other threads:[~2005-04-22 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20  8:11 Bug in MDADM or just crappy computer? Phantazm
2005-02-20  9:41 ` Phantazm
2005-02-20 10:38 ` Phantazm
2005-04-22 12:26 ` Molle Bestefich [this message]

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=62b0912f050422052612fac70a@mail.gmail.com \
    --to=molle.bestefich@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=phantazm@phantazm.nu \
    /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).