Re: Accesses to not yet running array
From: NeilBrown <hidden>
Date: 2013-08-26 04:33:49
Attachments
- signature.asc [application/pgp-signature] 828 bytes
From: NeilBrown <hidden>
Date: 2013-08-26 04:33:49
On Sat, 24 Aug 2013 20:41:19 +0200 Martin Wilck [off-list ref] wrote:
On 08/24/2013 02:42 PM, Francis Moreau wrote:quoted
On Sat, Aug 24, 2013 at 2:40 PM, Francis Moreau [off-list ref] wrote:quoted
Hello Martin, On Fri, Aug 23, 2013 at 9:09 PM, 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.oh, ok, I should have noticed.quoted
You'd avoid the problem by running "mdadm -IR /dev/sda" in the first place.Actually this is how arrays are assembled during boot on some distributions (Fedora for example).I meant the sequence: mdadm -I /dev/sda mdadm -I /dev/sdb mdadm -R /dev/mdxxx is used by distribution.CentOS 6 uses the following sequence: mdadm -I /dev/sda mdadm -I /dev/sdb mdadm -I /dev/mdXXX I don't see mdadm -R anywhere on CentOS. You could change your udev rules to run "mdadm -IR /dev/mdXXX" instead. Have you tried that? I wonder if that woudn't be smarter anyway. Neil?
I don't think you want the udev rules to run "mdadm -IR ...". If 'mdadm -IR...' to be run at all, it should probably be mdadm -IRs and it should happen after all attached busses have been scanned and udev has processed all new devices. NeilBrown