All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] ANNOUNCE: mdadm 2.5.1 - A tool for managing Soft RAID under Linux
Date: Mon, 19 Jun 2006 14:58:06 -0400	[thread overview]
Message-ID: <4496F3BE.9040707@steeleye.com> (raw)
In-Reply-To: <4496BE1A.8010502@steeleye.com>

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

> Neil Brown wrote:
> I am pleased to announce the availability of
>    mdadm version 2.5.1

What the heck, here's another one. :) This one is slightly more serious. 
We're getting a device of "0:0" in "Fail" events from the mdadm monitor 
sometimes now (due to the change in map_dev, which allows it to 
sometimes return "0:0" instead of just NULL for an unknown device).

The patch fixes my issue. I don't know if there are more.

Thanks,
Paul

[-- Attachment #2: mdadm-2.5.1-dev0:0-monitor-fix.diff --]
[-- Type: text/plain, Size: 430 bytes --]

--- mdadm-2.5.1/Monitor.c	Thu Jun  1 21:33:41 2006
+++ mdadm-2.5.1-new/Monitor.c	Mon Jun 19 14:51:31 2006
@@ -328,7 +328,7 @@ int Monitor(mddev_dev_t devlist,
 					}
 					disc.major = disc.minor = 0;
 				}
-				if (dv == NULL && st->devid[i])
+				if ((dv == NULL || strcmp(dv, "0:0") == 0) && st->devid[i])
 					dv = map_dev(major(st->devid[i]),
 						     minor(st->devid[i]), 1);
 				change = newstate ^ st->devstate[i];

  reply	other threads:[~2006-06-19 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16  1:03 ANNOUNCE: mdadm 2.5.1 - A tool for managing Soft RAID under Linux Neil Brown
2006-06-16 15:46 ` Paul Clements
2006-06-16 17:54   ` Bill Davidsen
2006-06-19 15:09     ` [PATCH] " Paul Clements
2006-06-19 18:58       ` Paul Clements [this message]
2006-06-20  0:04         ` Neil Brown
2006-06-19 19:02       ` Paul Clements
2006-06-17  2:12 ` mdadm 2.5.1 - A problem came up Mr. James W. Laferriere
2006-06-17  7:00   ` Neil Brown

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=4496F3BE.9040707@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.