RAID1: can't remove (or set-faulty) a disk during resync with mdadm

RAID1: can't remove (or set-faulty) a disk during resync with mdadm

[David Mansfield]

Hi,

I'm running on Centos 4.3 with the latest kernel so perhaps this is a 
'vendor uses old/modified kernel' problem, (kernel is 2.6.9-34.EL) but 
anyway here goes:

I have a degraded mirror.  The rebuild is proceeding with /dev/hda1 
'good' and /dev/hdb1 'syncing'.

I'd like to pull /dev/hdb1 out of the raid and go back to 'degraded' 
mode with no resync.

When I run mdadm --manage -f /dev/md1 /dev/hdb2 it only causes the 
resync to start again from the beginning, it doesn't actually mark it bad.

The same thing happens if there's a write error to /dev/hdb1 during 
resync, instead of failing, it simply restarts the resync.

I imagine the two are related - maybe 'set faulty' simply simulates an 
i/o error on the member, but during resync, the behavior is 'retry'.

Is there anything that can be done about this (other than politely ask 
vendor for a fix ;-)?

David

Re: RAID1: can't remove (or set-faulty) a disk during resync with mdadm

[Gil]

David Mansfield wrote:
> When I run mdadm --manage -f /dev/md1 /dev/hdb2 it only causes the
> resync to start again from the beginning, it doesn't actually mark it bad.

For grins, does mdadm --manage /dev/md1 -f /dev/hdb2 behave
differently?  Or just mdadm /dev/md1 -f /dev/hdb2?

I ran basically the last one on a CentOS 4.3 box not more than a
week ago and it was fine.

--Gil