Bug#601198: mdadm: Says it sets faulty even when it actually doesn't
found 601198 linux-2.6/2.6.32-41
tags 601198 + patch moreinfo
Mike Hommey wrote:
> Just had this scary experience this morning, where I thought I did
> something really wrong, being that I setted faulty the only remaining
> active device from a raid 1 array during recovery, when I meant to
> set the other one faulty:
> # mdadm --set-faulty /dev/md0 /dev/sdb2
> mdadm: set /dev/sdb2 faulty in /dev/md0
> Here I thought I was screwed, but it turns out it really didn't happen.
> For people's blood pressure, it would better if it managed to say it
> failed doing the requested operation.
Said to be fixed by v3.1-rc5~4^2~5 (md: report failure if a 'set
faulty' request doesn't, 2011-08-25).
Do you think this is worth fixing in squeeze? If so, please test the
From: NeilBrown <firstname.lastname@example.org>
Date: Thu, 25 Aug 2011 14:42:51 +1000
Subject: md: report failure if a 'set faulty' request doesn't.