From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Custom block script started twice for root block but only stopped once
Date: Tue, 4 Dec 2012 16:34:51 +0100 [thread overview]
Message-ID: <50BE181B.2040705@citrix.com> (raw)
In-Reply-To: <CAF6-1L7NyZgM4AhuT7fwz1+wL7gFqTufcEhsufA3SUHE4XVj3Q@mail.gmail.com>
On 04/12/12 16:23, Sylvain Munaut wrote:
> Actually I managed to trace it a bit further but here I'm kind of
> stuck due to my lack of knowledge of "how it should work".
>
> Basically it does try to destruct the device and the hotplug script
> '/etc/xen/scripts/block' is called with the command remove and the
> right device path. However by the time it's called, the corresponding
> subtree in the xenstore has been wiped it seems and so the hotplug
> script fails, not knowing what to do ... and it does nothing.
>
> So whoever triggers the hotplug remove action should leave the xen
> store tree in place until the hotplug script has run.
This is one of the reasons we no longer launch hotplug scripts from udev
in xl, it is difficult to synchronize the process, and this kind of
races can happen easily, I guess the same can happen in xend. I think
the best way to fix this would be to switch to Xen 4.2 and the xl toolstack.
next prev parent reply other threads:[~2012-12-04 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 10:37 Custom block script started twice for root block but only stopped once Sylvain Munaut
2012-11-08 8:26 ` Ian Campbell
2012-11-09 15:36 ` Roger Pau Monné
2012-11-09 15:46 ` Ian Campbell
2012-11-13 16:49 ` Roger Pau Monné
2012-11-26 13:45 ` Sylvain Munaut
2012-12-04 14:21 ` Sylvain Munaut
2012-12-04 15:23 ` Sylvain Munaut
2012-12-04 15:34 ` Roger Pau Monné [this message]
2012-12-04 15:28 ` Roger Pau Monné
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=50BE181B.2040705@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=s.munaut@whatever-company.com \
--cc=xen-devel@lists.xen.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).