From: Espen Berg <espen@monsternett.no>
To: kvm@vger.kernel.org
Subject: Corrupted filesystem, possible after livemigration with iSCSI storagebackend.
Date: Mon, 08 Mar 2010 11:02:40 +0100 [thread overview]
Message-ID: <4B94CB40.2070202@monsternett.no> (raw)
In our KVM system we have two iSCSI backends (master/slave
configuration) with failover and two KVM hosts supporting live migration.
The iSCSI volumes are shared by the host as a block device in KVM, and
the volumes are available on both frontends. After a reboot one of the
KVMs where not able to start again due to file system corruption. We
use XFS and have problems to understand what caused the corruption.
We have ruled out the iSCSI backend as both the master and slave data
where consistent at the time.
Anyone else had similar problems? What is the recommended way to share
an iSCSI drive among the two host machines?
Should XFS be ok as a file system for live migration? I'm not able to
find any documentation stating that a clustered file system (GFS2 etc.)
is recommended. Are there any concurrent writes on the two host
machines during a livemigtation?
<disk type='block' device='disk'>
<driver name='qemu'/>
<source dev='/dev/disk/by-path/ip-<ip>:3260-iscsi-test2-lun-0'/>
<target dev='sda' bus='scsi'/>
<address type='drive' controller='0' bus='0' unit='0'/>
</disk>
#virsh version
Compiled against library: libvir 0.7.6
Using library: libvir 0.7.6
Using API: QEMU 0.7.6
Running hypervisor: QEMU 0.11.0
#uname -a
Linux vm01 2.6.32-bpo.2-amd64 #1 SMP Fri Feb 12 16:50:27 UTC 2010 x86_64
GNU/Linux
Regards
Espen
reply other threads:[~2010-03-08 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B94CB40.2070202@monsternett.no \
--to=espen@monsternett.no \
--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