Re: [Patch] mdadm ignoring homehost?

[Doug Ledford <dledford@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

On Apr 22, 2009, at 12:06 PM, Andrew Burgess wrote:
> On Tue, 2009-04-21 at 20:15 +0200, Piergiorgio Sartor wrote:
>
>> This might be a Fedora 10 issue, so maybe Doug would like
>> to comment.
>>
>> After reboot, someone, I guess udev, tries to automagically
>> start a RAID, so it assembles /dev/md_d127 with one of the
>> two components of /dev/md/boot (randomly, it seems).
>> Later, when /dev/md/boot is assembled, one drive is "busy",
>> because it belongs to /dev/md_d127, and the array is put
>> together degraded, i.e. with the other disk only.
>
> Just a "me too". I also started seeing this after upgrading to fedora
> 10. I had to create a startup script to stop md_d0 and reassemble
> everything else.


Yeah, I found the cause for this while working on F11.  The problem is  
a race condition between udev and a call to mdadm -As in the  
rc.sysinit.  For F11, I solved this by making udev not process devices  
using incremental mode if we are still in the rc.sysinit script.  You  
can change /etc/udev/rules.d/70-mdadm.rules (I think that's the right  
name, it might be slightly off) to read something like this:

# This file causes block devices with Linux RAID (mdadm) signatures to
# automatically cause mdadm to be run.
# See udev(8) for syntax

SUBSYSTEM=="block", ACTION=="add",  
ENV{ID_FS_TYPE}=="linux_raid_member", \
	IMPORT{program}="/sbin/mdadm --examine --export $tempnode", \
	RUN+="/bin/bash -c '[ ! -f /dev/.in_sysinit ] && mdadm -I  
$env{DEVNAME}'"



--

Doug Ledford <dledford@redhat.com>

GPG KeyID: CFBFF194
http://people.redhat.com/dledford

InfiniBand Specific RPMS
http://people.redhat.com/dledford/Infiniband





[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 203 bytes --]