Kevin,<div>I modified the VMFS virtual disk to Independent, and I haven't seen the issue since the change Friday morning. I noticed this didn't work for you. I will continue to watch it and let the list know. The issue I saw after several weeks was the data was not in sync. Two nodes saw different data on the same OCFS2 drive. </div>
<div><br></div><div>We have Vsphere 4.1, and HP EVA 3000 SAN. </div><div><br></div><div>Thanks,</div><div><br></div><div><br><br><div class="gmail_quote">On Sat, Dec 11, 2010 at 10:41 AM, <span dir="ltr"><<a href="mailto:kevin@utahsysadmin.com">kevin@utahsysadmin.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Fri, 10 Dec 2010 06:26:06 -0800, <a href="mailto:ocfs2-users-request@oracle.com">ocfs2-users-request@oracle.com</a> wrote:<br>
><br>
> My setup has the SCSI controller set to Physical so the guest can be on<br>
> different hosts, but I do not have the disk setup as Independent. I am<br>
> going<br>
> to change that setting in VMware and see if it makes a difference.<br>
><br>
</div><div class="im">> > [2037805.922718] end_request: I/O error, dev sdb, sector 1735<br>
> > [2037805.922974] (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5<br>
> > [2037805.923370] (27506,0):o2hb_do_disk_heartbeat:753 ERROR: status =<br>
-5<br>
<br>
</div>Brad,<br>
<br>
I have had the same issue for over a year on ESX 3.5 as well as on vSphere<br>
4.0. I have not tried yet on 4.1. The error occurs when I put the shared<br>
disk on either SATA or FC LUNs on our SAN. It also doesn't matter if the<br>
virtual machines are on the same physical host or not (with independent<br>
disks). The only problem that has come from it is the occasional reboot of<br>
one of the VMs, which for me is tolerable. I keep hoping to upgrade to a<br>
new SAN thinking that might fix it. The vSphere 4.0 release IOPS<br>
capability is higher than the SAN (it's 5 years old) so I didn't think it<br>
was VMware's fault. If you have fairly new hardware, maybe there is a real<br>
bug somewhere. I don't get I/O errors in any of my other implementations<br>
on this SAN. I sent a post like yours to the list when I first built it,<br>
but never opened a bug report with either OCFS or VMware. If you create a<br>
bug report I could add information from my implementation as well. (I<br>
actually have two of these setups and they both have the same errors.)<br>
<br>
Of course, if you find a solution, please post that as well.<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<br>
</blockquote></div><br></div>