Thread (5 messages) 5 messages, 2 authors, 2011-07-14

Re: possible bug in md

From: NeilBrown <hidden>
Date: 2011-07-14 05:11:37

On Tue, 05 Jul 2011 12:25:39 -0400 Iordan Iordanov [off-list ref]
wrote:
Hi Neil,

On 07/04/11 20:24, NeilBrown wrote:
quoted
This is correct in that the spare should be removed from the array as there
is nothing else useful that can be done.  It is possibly not ideal in that
the spare gets marked as 'faulty' where it isn't really.
I agree that MD is doing the right thing in stopping the sync, since 
there is nothing else that can be done. What it should say in the kernel 
log in this case (in my opinion anyway) is something like:

raid10: Disk failure on sda, sync stopped, sdb marked faulty.

instead of:

raid10: Disk failure on sdb, disabling device.

only because /dev/sdb did not actually fail! I agree this is not 
terribly important, I was reporting only for correctness, and I know 
you're busy :).

Many thanks,
Iordan
I have made some changes to RAID10 so that it will not report that
a device has failed when really it hasn't.  It will abort the recovery,
ensure that another recovery doesn't automatically restart, and will
report why the recovery was aborted.

Thanks,
NeilBrown
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help