Re: Accesses to not yet running array

[NeilBrown <neilb@suse.de>]

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

On Mon, 26 Aug 2013 09:30:04 +0200 Francis Moreau <francis.moro@gmail.com>
wrote:

> Hello Neil,
> 
> On Mon, Aug 26, 2013 at 7:30 AM, NeilBrown <neilb@suse.de> wrote:
> > On Fri, 23 Aug 2013 21:09:24 +0200 Martin Wilck <mwilck@arcor.de> wrote:
> >
> >> On 08/23/2013 12:00 PM, Francis Moreau wrote:
> >>
> >> > [ adding Martin in CC since it seems related to DDF... ]
> >>
> >> I reproduced it here. The problem is that mdmon isn't running. Simply
> >> try running "mdmon /dev/md127", and the mount should proceed.
> >>
> >> You'd avoid the problem by running "mdadm -IR /dev/sda" in the first place.
> >>
> >> @Neil: This is unexpected, I think we need some code to start mdmon if
> >> necessary in Manage_run. I considered coming up with a patch, but you
> >> can do it much quicker, I think.
> >>
> >
> > I've changed Manage_run() to call the same code that "mdadm -IRs" call, but
> > asking to just run the one array, not all arrays.
> > This should  do what is expected (I hope).
> 
> 
> Any chance to get the same fix for 3.2.x release ?

I think it would be a lot easier to just remove the "mdadm -R ..." calls.
Where exactly are they?  In some /etc/init.d script?

You probably want "mdadm -IRs" there.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]