From: "Phantazm" <phantazm@phantazm.nu>
To: linux-raid@vger.kernel.org
Subject: Bug in MDADM or just crappy computer?
Date: Sun, 20 Feb 2005 09:11:29 +0100 [thread overview]
Message-ID: <cv9gbc$84g$1@sea.gmane.org> (raw)
My resync problem still goes on :-(
When the resync is done on my raid5 with 8 disks just goes into a loop and
marks 2 disks as failed.
Then i need to reboot and assemble them again with the force. (the 2 disks
thats failing isnt on same controller card)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
aint got a single clue what it could be.
I have tried this patch too..
(The disks are not broken, that i know for sure)
--------------------------------------------
Fix endless loop when syncing an array that doesn't need any resync.
If the resync checkpoint for an array is at the end of the array, It doesn't
get set to MAX_SECTOR, so resyncing will be retried.
By updating curr_resync early, this problem is fixed.
Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>
### Diffstat output
./drivers/md/md.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~ 2005-02-02 12:08:42.000000000 +1100
+++ ./drivers/md/md.c 2005-02-02 12:08:53.000000000 +1100
@@ -3472,10 +3472,12 @@ static void md_do_sync(mddev_t *mddev)
init_waitqueue_head(&mddev->recovery_wait);
last_check = 0;
- if (j)
+ if (j>2) {
printk(KERN_INFO
"md: resuming recovery of %s from checkpoint.\n",
mdname(mddev));
+ mddev->curr_resync = j;
+ }
while (j < max_sectors) {
int sectors;
@@ -3562,7 +3564,7 @@ static void md_do_sync(mddev_t *mddev)
if (!test_bit(MD_RECOVERY_ERR, &mddev->recovery) &&
mddev->curr_resync > 2 &&
- mddev->curr_resync > mddev->recovery_cp) {
+ mddev->curr_resync >= mddev->recovery_cp) {
if (test_bit(MD_RECOVERY_INTR, &mddev->recovery)) {
printk(KERN_INFO
"md: checkpointing recovery of %s.\n",
next reply other threads:[~2005-02-20 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 8:11 Phantazm [this message]
2005-02-20 9:41 ` Bug in MDADM or just crappy computer? Phantazm
2005-02-20 10:38 ` Phantazm
2005-04-22 12:26 ` Molle Bestefich
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='cv9gbc$84g$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 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).