From: Anthony Liguori <anthony@codemonkey.ws>
To: Espen Berg <espen@monsternett.no>
Cc: kvm@vger.kernel.org
Subject: Re: Fwd: Corrupted filesystem, possible after livemigration with iSCSI storagebackend.
Date: Mon, 15 Mar 2010 08:59:10 -0500 [thread overview]
Message-ID: <4B9E3D2E.5090108@codemonkey.ws> (raw)
In-Reply-To: <4B9E3A37.5000209@monsternett.no>
On 03/15/2010 08:46 AM, Espen Berg wrote:
> 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>
You need to use cache=off if you've got one iscsi drive mounted on two
separate physical machines.
The additional layer of caching will result in inconsistency because
iSCSI doesn't have a mechanism to provide cache coherence between two nodes.
Regards,
Anthony Liguori
> #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
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-15 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 13:46 Fwd: Corrupted filesystem, possible after livemigration with iSCSI storagebackend Espen Berg
2010-03-15 13:59 ` Anthony Liguori [this message]
2010-03-15 14:25 ` Daniel P. Berrange
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=4B9E3D2E.5090108@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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