sd 1:0:0:0: reservation conflict That's the cause of the error in the guest. You'll have to track the error to ESX's management domain. See the logs.
Does this error come repeatedly? This error is only a problem for o2hb if it continues for the next 60 secs. Else it can be ignored. On 12/14/2010 07:20 AM, brad hancock wrote:
The issue is starting to come up again. Both machines are logging the error a couple of minutes apart from each other. sd 1:0:0:0: reservation conflict Dec 13 16:40:07 mdcvmsmes01 kernel: [295051.378262] sd 1:0:0:0: [sdb] Result: hostbyte=DID_OK d Dec 13 16:40:07 mdcvmsmes01 kernel: [295051.378347] end_request: I/O error, dev sdb, sector 173 Dec 13 16:40:07 mdcvmsmes01 kernel: [295051.378694] (0,1):o2hb_bio_end_io:225 ERROR: IO Error - Dec 13 16:40:07 mdcvmsmes01 kernel: [295051.379055] (1897,1):o2hb_do_disk_heartbeat:753 ERROR: Should I open a bug report? Who with, VMware or Oracle? On Sun, Dec 12, 2010 at 9:25 AM, brad hancock <braddhanc...@gmail.com <mailto:braddhanc...@gmail.com>> wrote: Kevin, 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. We have Vsphere 4.1, and HP EVA 3000 SAN. Thanks, On Sat, Dec 11, 2010 at 10:41 AM, <ke...@utahsysadmin.com <mailto:ke...@utahsysadmin.com>> wrote: On Fri, 10 Dec 2010 06:26:06 -0800, ocfs2-users-requ...@oracle.com <mailto:ocfs2-users-requ...@oracle.com> wrote: > > My setup has the SCSI controller set to Physical so the guest can be on > different hosts, but I do not have the disk setup as Independent. I am > going > to change that setting in VMware and see if it makes a difference. > > > [2037805.922718] end_request: I/O error, dev sdb, sector 1735 > > [2037805.922974] (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5 > > [2037805.923370] (27506,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5 Brad, I have had the same issue for over a year on ESX 3.5 as well as on vSphere 4.0. I have not tried yet on 4.1. The error occurs when I put the shared disk on either SATA or FC LUNs on our SAN. It also doesn't matter if the virtual machines are on the same physical host or not (with independent disks). The only problem that has come from it is the occasional reboot of one of the VMs, which for me is tolerable. I keep hoping to upgrade to a new SAN thinking that might fix it. The vSphere 4.0 release IOPS capability is higher than the SAN (it's 5 years old) so I didn't think it was VMware's fault. If you have fairly new hardware, maybe there is a real bug somewhere. I don't get I/O errors in any of my other implementations on this SAN. I sent a post like yours to the list when I first built it, but never opened a bug report with either OCFS or VMware. If you create a bug report I could add information from my implementation as well. (I actually have two of these setups and they both have the same errors.) Of course, if you find a solution, please post that as well. Thanks, Kevin _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
