Bug#767243: mdadm: a new disk always remains spare instead of becoming active

[Michael Tokarev]

29.10.2014 17:44, Matija Nalis wrote:
> Package: mdadm
> Version: 3.2.5-5
> Severity: normal
> 
> The problem is that newly added disk in 2-device RAID1 (intended to replace
> failing disk) is remaining as 'spare' and cannot be made active.
[...]

Just a quick note, so you wont wait for a reply.

>From the description in your email it looks like you have some prob
on one of the disks (either the one FROM which you're syncing data,
or the one TO which you write, ie, new), that's why you can't make
2 devices active.

But the whole thing does not look like a bug really, not at all,
and you've shown multiple user/usage errors (eg, mdadm --grow -n 2 --
ofcourse mdadm tells you there's nothing to change because the
array already is configured to be 2-way mirror).

It looks much more like a user support question.  But please understand
that BTS is definitely not the right place to ask for support, it is
a bug tracking system.

I haven't read your problem report in full details, just because I
don't have time now to understand your situation properly.  And since
it does not look like a bug, I'll close this bugreport soon (after
letting it to idle for some time, just in case).

This is to tell you to not expect replies, at least from me, at least
in a reasonable timeframe.

Thanks,

/mjt