linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: tomka@avaxio.net
Cc: "Linux, Raid lista" <linux-raid@vger.kernel.org>
Subject: Re: spare group
Date: Tue, 12 Jun 2007 19:54:28 +1000	[thread overview]
Message-ID: <18030.27988.798462.933425@notabene.brown> (raw)
In-Reply-To: message from Tomka Gergely on Tuesday June 12

On Tuesday June 12, tomka@avaxio.net wrote:
> 
> I am very sorry, but it wont works with .9 superblocks also :( We 
> missing something small, but important here. Before you start to code. 
> mdadm was running in monitor mode, and reported a Fail. mdadm is the 
> latest version, 2.6.2.
> 
> tg

Hmmm..... 
[tests code]

Yes, you are right.  It looks like a bug was introduced in 2.6 which
broke various aspects of --monitor.  I guess I need to add some
--monitor tests to my regression test suite.

This patch should fix it.

Thanks again,
NeilBrown


-------------------------------
Fix spare migration and other problems with --monitor.

2.6 broke --monitor in various ways, including spare migration
stopped working.  This fixes it.


### Diffstat output
 ./Monitor.c |    1 +
 1 file changed, 1 insertion(+)

diff .prev/Monitor.c ./Monitor.c
--- .prev/Monitor.c	2007-02-22 14:59:11.000000000 +1100
+++ ./Monitor.c	2007-06-12 19:48:34.000000000 +1000
@@ -328,6 +328,7 @@ int Monitor(mddev_dev_t devlist,
 			for (i=0; i<MaxDisks && i <= array.raid_disks + array.nr_disks;
 			     i++) {
 				mdu_disk_info_t disc;
+				disc.number = i;
 				if (ioctl(fd, GET_DISK_INFO, &disc) >= 0) {
 					info[i].state = disc.state;
 					info[i].major = disc.major;

  reply	other threads:[~2007-06-12  9:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 13:45 spare group Tomka Gergely
2007-06-11 23:47 ` Neil Brown
2007-06-12  6:34   ` Tomka Gergely
2007-06-12  6:59     ` Neil Brown
2007-06-12  7:57       ` Tomka Gergely
2007-06-12  9:54         ` Neil Brown [this message]
2007-06-13  7:25           ` Tomka Gergely

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=18030.27988.798462.933425@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=tomka@avaxio.net \
    /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).