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 14:02:34 +1100 [thread overview]
Message-ID: <87poltfq2d.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20161118023144.GC1804@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On Fri, Nov 18 2016, Andy Smith wrote:
> Hi Neil,
>
> On Fri, Nov 18, 2016 at 09:43:44AM +1100, NeilBrown wrote:
>> Something you could try, after boot and while the arrays are still not
>> assembled, is
>>
>> echo change > /sys/block/sdc/uevent
>> echo change > /sys/block/sdd/uevent
>>
>> That should cause udev to assemble the array.
>
> Nothing appeared to happen. There was nothing interesting in syslog
> or systemd's journal. Here's the output from "udevadm monitor":
OK, we are getting closer. That is good.
>
> $ sudo udevadm monitor
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
>
> KERNEL[12376.719100] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:0/end_device-10:0/target10:0:0/10:0:0:0/block/sdc (block)
> UDEV [12376.722996] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:0/end_device-10:0/target10:0:0/10:0:0:0/block/sdc (block)
> KERNEL[12388.329566] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:1/end_device-10:1/target10:0:1/10:0:1:0/block/sdd (block)
> UDEV [12388.333441] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/host10/port-10:1/end_device-10:1/target10:0:1/10:0:1:0/block/sdd (block)
>
>> If that doesn't work, the looking over the udev logs, and possibly
>> turning on extra udev logging, might lead to an answer.
>
> I don't know how to do that, but I'll look into it - thanks.
udevadm control -l debug
might help.
NeilBrown
>
> Cheers,
> Andy
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-18 3:02 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 [this message]
2016-11-18 3:47 ` Andy Smith
2016-11-18 4:08 ` NeilBrown
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=87poltfq2d.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).