From: NeilBrown <neilb@suse.com>
To: Andy Smith <andy@strugglers.net>
Cc: linux-raid@vger.kernel.org, 784070@bugs.debian.org
Subject: Re: Newly-created arrays don't auto-assemble - related to hostname change?
Date: Wed, 23 Nov 2016 13:34:52 +1100 [thread overview]
Message-ID: <87wpfuc4ab.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20161122060105.GS1804@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Tue, Nov 22 2016, Andy Smith wrote:
> Hi Neil,
>
> On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote:
>> Thanks. Sorry this is taking a lot of back-and-forth...
>
> No worries. This is very interesting to me and I'd also like to know
> what is going wrong even if I have a work-around.
Thanks.
I tried this on a scratch Debian VM I had lying around, and found I
could exactly reproduce your symptoms.
I found that, unlike on the first Debian system I looked at, there is a
line in /lib/udev/rules.d/64-md-raid-assembly.rules
# Disable incremental assembly to fix Debian bug #784070
GOTO="md_inc_end"
Remove that and the problem goes away. Arrgg...
I wish people maintainers would *ask* upstream when they don't
understand, rather than just breaking things.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-23 2:34 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
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 [this message]
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=87wpfuc4ab.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=784070@bugs.debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.