linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-raid@vger.kernel.org
Subject: Re: [Patch] mdadm ignoring homehost?
Date: Thu, 23 Apr 2009 07:51:32 +0200	[thread overview]
Message-ID: <20090423055132.GA29487@maude.comedia.it> (raw)
In-Reply-To: <9A77DB27-C12A-4BA2-94C4-D59B7DAFF32C@redhat.com>

On Wed, Apr 22, 2009 at 09:20:49PM -0400, Doug Ledford wrote:
> 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}'"
>
>

i believe i saw this as well, but not at startup, it was when i manually
run mdadm -As, so while your hack to prevent udev from assembling
devices while in sysinit may not be a full solution.

my solution was "rm -f /etc/udev/rules.d/70-mdadm.rules",
works like a charm :P

probably the best solution is preventing concurrent mdadm rules with a
lock.

Regards,
L.




-- 
Luca Berra -- bluca@comedia.it
         Communication Media & Services S.r.l.
  /"\
  \ /     ASCII RIBBON CAMPAIGN
   X        AGAINST HTML MAIL
  / \

  reply	other threads:[~2009-04-23  5:51 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 16:57 mdadm ignoring homehost? Jon Nelson
2009-04-01 15:15 ` Jon Nelson
2009-04-01 22:46   ` Neil Brown
2009-04-06 14:47     ` [Patch] " Doug Ledford
2009-04-06 19:33       ` Luca Berra
2009-04-17  3:49       ` Neil Brown
2009-04-17  7:08         ` Gabor Gombas
2009-04-20  5:23           ` Neil Brown
2009-04-21  6:34             ` Gabor Gombas
2009-04-21  7:06               ` Luca Berra
2009-04-17 18:17         ` Doug Ledford
2009-04-17 18:40           ` Piergiorgio Sartor
2009-04-18  7:54             ` Luca Berra
2009-04-18  8:36               ` Piergiorgio Sartor
2009-04-18 10:19                 ` Luca Berra
2009-04-18 13:06                   ` Piergiorgio Sartor
2009-04-20  5:58                     ` Neil Brown
2009-04-20 12:29                       ` Doug Ledford
2009-04-20 18:17                       ` Piergiorgio Sartor
2009-04-20 19:49                         ` Leslie Rhorer
2009-04-20 20:04                           ` Piergiorgio Sartor
2009-04-20 21:18                           ` Luca Berra
2009-04-20 21:13                         ` Luca Berra
2009-04-20 21:24                           ` Piergiorgio Sartor
2009-04-20 23:47                             ` Doug Ledford
2009-04-21  0:00                               ` Doug Ledford
2009-04-21  8:57                                 ` Michal Soltys
2009-04-21  6:29                               ` Luca Berra
2009-04-21 18:15                           ` Piergiorgio Sartor
2009-04-22 16:06                             ` Andrew Burgess
2009-04-23  1:20                               ` Doug Ledford
2009-04-23  5:51                                 ` Luca Berra [this message]
2009-04-23  6:09                                   ` Luca Berra
2009-04-23 11:05                                   ` Doug Ledford
2009-04-23 21:31                                     ` Luca Berra
2009-04-24 16:46                                       ` Doug Ledford
2009-04-24 19:15                                 ` Piergiorgio Sartor
2009-04-26 11:52                                   ` Doug Ledford
2009-04-26 12:14                                     ` Piergiorgio Sartor
2009-04-26 12:58                                       ` Piergiorgio Sartor
2009-04-26 18:06                                         ` Doug Ledford
2009-04-26 19:08                                           ` Piergiorgio Sartor
2009-04-26 21:37                                       ` Michal Soltys
2009-04-18 14:34             ` Andrew Burgess
2009-04-18  8:12           ` Luca Berra
2009-04-18  8:44             ` Piergiorgio Sartor
2009-04-18 13:35             ` Doug Ledford
2009-04-18 13:52               ` Piergiorgio Sartor
2009-04-18 14:50                 ` Doug Ledford
2009-04-18 14:48               ` Jon Nelson
2009-04-20  6:08               ` Neil Brown
2009-04-20 12:26                 ` Luca Berra
2009-04-20 12:36                 ` Doug Ledford
2009-04-18 13:58           ` Bill Davidsen
2009-04-20  7:23           ` Neil Brown
2009-04-20 13:15             ` Doug Ledford
2009-04-21  6:54               ` Neil Brown
2009-05-11  6:47               ` Neil Brown
2009-04-01 22:47 ` Michal Soltys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090423055132.GA29487@maude.comedia.it \
    --to=bluca@comedia.it \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).