From: NeilBrown <neilb@suse.de>
To: NeilBrown <neilb@suse.de>
Cc: Adam Kwolek <adam.kwolek@intel.com>,
linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 1/2] md/raid5: FIX: manually-added spare is not used
Date: Mon, 17 Jan 2011 10:28:21 +1100 [thread overview]
Message-ID: <20110117102821.3460a918@notabene.brown> (raw)
In-Reply-To: <20110117101128.60a9b683@notabene.brown>
On Mon, 17 Jan 2011 10:11:28 +1100 NeilBrown <neilb@suse.de> wrote:
> On Fri, 14 Jan 2011 14:00:00 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
>
> > Manually added spares are not used due to fact that they not added to md configuration.
> > Counters are updated only.
> >
> > Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> > ---
> >
> > drivers/md/raid5.c | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> > index a2087c7..59c4150 100644
> > --- a/drivers/md/raid5.c
> > +++ b/drivers/md/raid5.c
> > @@ -5592,8 +5592,10 @@ static int raid5_start_reshape(mddev_t *mddev)
> > } else if (rdev->raid_disk >= conf->previous_raid_disks
> > && !test_bit(Faulty, &rdev->flags)) {
> > /* This is a spare that was manually added */
> > - set_bit(In_sync, &rdev->flags);
> > - added_devices++;
> > + if (raid5_add_disk(mddev, rdev) == 0) {
> > + set_bit(In_sync, &rdev->flags);
> > + added_devices++;
> > + }
> > }
> >
> > /* When a reshape changes the number of devices, ->degraded
>
> This should not be needed.
> When a device is manually added, the desired slot number is written to
> ..../md/dev-XXX/slot
>
> This calls slot_store (in md.c) which call mddev->pers->hot_add_disk which
> for raid5 is raid5_add_disk.
> So you shouldn't need to call raid5_add_disk again.
>
ahhh... I see. raid5_add_disk doesn't do the right thing in that case. It
actually indexes beyond the end of an array, which is bad.
We possibly do need the raid5_add_disk where you had put it. I'll have a
think and see what is best.
Thanks,
NeilBrown
next prev parent reply other threads:[~2011-01-16 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 12:59 [PATCH 0/2] fixes for manually-added spares in raid5 (2nd) Adam Kwolek
2011-01-14 13:00 ` [PATCH 1/2] md/raid5: FIX: manually-added spare is not used Adam Kwolek
2011-01-16 23:11 ` NeilBrown
2011-01-16 23:28 ` NeilBrown [this message]
2011-01-17 0:44 ` NeilBrown
2011-01-17 14:13 ` Kwolek, Adam
2011-01-19 20:48 ` NeilBrown
2011-01-20 8:29 ` Kwolek, Adam
2011-01-20 9:30 ` NeilBrown
2011-01-20 9:40 ` Kwolek, Adam
2011-01-20 10:15 ` NeilBrown
2011-01-14 13:00 ` [PATCH 2/2] md/raid5: FIX: reshape on degraded devices has wrong configuration Adam Kwolek
2011-01-16 23:30 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 12:38 [PATCH 0/2] fixes for manually-added spares in raid5 Adam Kwolek
2011-01-14 12:38 ` [PATCH 1/2] md/raid5: FIX: manually-added spare is not used Adam Kwolek
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=20110117102821.3460a918@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=wojciech.neubauer@intel.com \
/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).