From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: KVM list <kvm@vger.kernel.org>
Subject: Question: data consistency on fail-over using shared disk
Date: Wed, 21 Jul 2010 15:27:28 +0900 [thread overview]
Message-ID: <4C469350.3080008@oss.ntt.co.jp> (raw)
Hi,
We are now checking about what we should do on vm fail-over.
Concerning this, does anybody know about any danger about data
consistency when we are using shared disk?
What I'm concerning is if crashed VM-side host is still holding
buffered data, starting a new VM instance on another node may
result in file system corruption.
This problem may similar to live-migration but little bit different
in the sense that VM is crashed -> cannot do anything from that point.
How about the combination of old or new guest OS and the following
settings?
- writethrough
- writeback
- none
If needed, we'll do sync by HA-side scripts before starting a new VM
instance.
Thanks,
Takuya
next reply other threads:[~2010-07-21 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 6:27 Takuya Yoshikawa [this message]
2010-07-21 7:27 ` Question: data consistency on fail-over using shared disk Avi Kivity
2010-07-21 7:43 ` Takuya Yoshikawa
2010-07-21 10:46 ` Avi Kivity
2010-07-22 0:41 ` Fernando Luis Vázquez Cao
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=4C469350.3080008@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=kvm@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