All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Migration filesystem coherency?
Date: Tue, 27 Jun 2006 12:29:56 -0700	[thread overview]
Message-ID: <44A18734.5010704@hp.com> (raw)


Hi,

I thought I had a workaround for live migration crashing (I've been 
looking at the SLES 3.0.2 9742c code.), but I found that I was getting 
filesystem errors. I'm wondering if the problem is races in data being 
written to the backing storage.

When migrating a domain, before the domain is started on the new host, 
you have to guarantee that all the domU vbd data is out of the block 
cache and written to the backing device. (In the case of a loopback 
device, whether this is sufficient depends on the cross-host coherency 
guarantees of the backing filesystem.) I cannot see that this takes 
place synchronously with the migration process. To me it looks like that 
the teardown/flush of the backing device depends on the action of the 
xenbus and the hotplug scripts and looks asynchronous to the migration 
process.

So, am I right that there is a really a problem here or is there some 
other way the vbd data is getting flushed during migrate?

Thanks,

John Byrne

             reply	other threads:[~2006-06-27 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 19:29 John Byrne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-27 20:39 Migration filesystem coherency? Ian Pratt
2006-06-27 22:08 ` John Byrne
2006-06-28 16:34   ` Charles Coffing

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=44A18734.5010704@hp.com \
    --to=john.l.byrne@hp.com \
    --cc=xen-devel@lists.xensource.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 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.