From: NeilBrown <neilb@suse.com>
To: Andy Smith <andy@strugglers.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Newly-created arrays don't auto-assemble - related to hostname change?
Date: Fri, 18 Nov 2016 15:08:23 +1100 [thread overview]
Message-ID: <87k2c1fn0o.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20161118034716.GI21587@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
On Fri, Nov 18 2016, Andy Smith wrote:
>
> Am I right in thinking this is not incremental assembly by udev, but
> kernel auto-assembly?
That isn't kernel auto-assembly, but it doesn't look like incremental
assembly either.
/usr/share/initramfs-tools/scripts/local-block/mdadm
runs
mdadm -q --assemble --scan --no-degraded
to start all the arrays that the initramfs can find. So it is
mdadm-based auto-assembly.
>
> Also, in the previous configuration, mpt3sas was being loaded once
> the root filesystem had been mounted. All the drives on the SAS
> controller were then available, so udev should have assembled md5 at
> that point, right? So I think there is still a problem here, just
> one which I have worked around in some other way.
Yes, I think there is still a problem. When the mpt3sas is loaded udev
should trigger the arrays to be created.
>
> If that is the case, would you like me to continue debugging udev?
Up to you, but I have an idea.
The udev rules files depends on 'blkid' having been run.
/lib/udev/rules.d/60-persistent-storage.rules
does this, but not for
KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*|zram*|mmcblk[0-9]*rpmb"
... though that wouldn't apply to you.
what does
udevadm info /dev/sdc
report?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-18 4:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 3:52 Newly-created arrays don't auto-assemble - related to hostname change? Andy Smith
2016-11-17 6:09 ` NeilBrown
2016-11-17 15:09 ` Andy Smith
2016-11-17 22:43 ` NeilBrown
2016-11-18 2:31 ` Andy Smith
2016-11-18 3:02 ` NeilBrown
2016-11-18 3:47 ` Andy Smith
2016-11-18 4:08 ` NeilBrown [this message]
2016-11-18 4:17 ` Andy Smith
2016-11-21 4:32 ` NeilBrown
2016-11-21 6:02 ` Andy Smith
2016-11-21 22:56 ` NeilBrown
2016-11-22 6:01 ` Andy Smith
2016-11-23 2:34 ` NeilBrown
2016-11-23 9:03 ` Bug#784070: " Michael Tokarev
2016-11-24 1:24 ` Andy Smith
2016-11-23 9:09 ` SOUBEYRAND Yann - externe
2016-11-17 23:22 ` Peter Sangas
2016-11-18 2:03 ` Glenn Enright
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=87k2c1fn0o.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=andy@strugglers.net \
--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).