Re: Accesses to not yet running array
From: Francis Moreau <hidden>
Date: 2013-08-26 08:16:34
On Mon, Aug 26, 2013 at 9:53 AM, NeilBrown [off-list ref] wrote:
On Mon, 26 Aug 2013 09:30:04 +0200 Francis Moreau [off-list ref] wrote:quoted
Hello Neil, On Mon, Aug 26, 2013 at 7:30 AM, NeilBrown [off-list ref] wrote:quoted
On Fri, 23 Aug 2013 21:09:24 +0200 Martin Wilck [off-list ref] wrote:quoted
On 08/23/2013 12:00 PM, Francis Moreau wrote:quoted
[ 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?
Nope, it's in the initrd, in my case generated by dracut. Did you mean removing "mdadm -R ..." and add "mdadm -IRs ..." instead ?
You probably want "mdadm -IRs" there.
Well, I thought there was a difference between running "mdadm -IRs" and the fix you did in Manage_run() and your fix was preferred. -- Francis