From: SOUBEYRAND Yann - externe <yann-externe.soubeyrand@edf.fr>
To: "neilb@suse.com" <neilb@suse.com>,
"784070@bugs.debian.org" <784070@bugs.debian.org>
Cc: "andy@strugglers.net" <andy@strugglers.net>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?
Date: Wed, 23 Nov 2016 09:09:12 +0000 [thread overview]
Message-ID: <1479892151.10140.3.camel@edf.fr> (raw)
In-Reply-To: <87wpfuc4ab.fsf@notabene.neil.brown.name>
Le mercredi 23 novembre 2016 à 13:34 +1100, neilb@suse.com a écrit :
> 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
Hi Neil,
I encourage you to have a look at the full history of this bug to see
why this line was introduced. You will then see that it has been removed
in Stretch.
Regards
Yann
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.
Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________
This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.
If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.
E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
next prev parent reply other threads:[~2016-11-23 9:09 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
2016-11-23 9:03 ` Bug#784070: " Michael Tokarev
2016-11-24 1:24 ` Andy Smith
2016-11-23 9:09 ` SOUBEYRAND Yann - externe [this message]
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=1479892151.10140.3.camel@edf.fr \
--to=yann-externe.soubeyrand@edf.fr \
--cc=784070@bugs.debian.org \
--cc=andy@strugglers.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
/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).