Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Both hosts are Fedora 13. We use dm-multipath (multipathd). Qemu-kvm is the hypervisor.
The problem is that when host1 writes something to the SAN host 2
won't see it until the host reestablishes a connection to the LUN (i.e. log of the iscsi targets and log in again). So writing a file on the LUN by host1 is not visible by host2 which has also mounted that LUN.
The consequense of the cachingproblem is that when a VM migrates to the other host it will crash because the virtual disk is different for host 1 and 2. Migrating with Qemu-kvm succeeds when both hosts are just rebooted.
Does anyone have a clue which component is caching? Is it the MD3000i itself? iSCSI-client (iscsiadm)? Multipathd? LVM?
Thanks advance
Last edited by boeboe2005; 09-20-2010 at 08:41 AM.
Thanks a lot for this great tip dyasny! I'll try it out.
I can understand that writing simultaniously to the same shared lun by host1 and host2 would screw up the files but does it also explains why changes made by host1 are not seen by host2 (which only reads)?
Thanks a lot for this great tip dyasny! I'll try it out.
I can understand that writing simultaniously to the same shared lun by host1 and host2 would screw up the files but does it also explains why changes made by host1 are not seen by host2 (which only reads)?
thanks for your help!
Yes, that explains it. If you use a clustered FS, you will be able to see the changes from all the nodes right away
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.