Re: [Ocfs2-users] Reservation conflicts

[Antonis Kopsaftis]

We use RDM in our (production) setup for almost 15months at its works
without problems.
Initially we used ocfs2, but the last month we switched to gfs2, as
oracle decided to stop fixing  bugs on redhat 5.x OS.

We have also tried vmware disk sharing  in lab environment (with gfs2),
and we have not experienced any problems. As far
i know, vmware disk sharing it's supposed to be a production quality
feature according to vmware.

akops

On 15/12/2010 8:17 ??, Sunil Mushran wrote:
> Ideally the scsi reservation error should be trapped by hypervisor/mgmt
> domain and should not bubble upto the guest. That is if vmfs is doing the
> reservation. Have you looked into the logs on all machines? See if there
> is a way to get vmfs to log that info.
>
> As far as RDM's goes, that's how I believe people use it. But you'll
> have to
> get confirmation from actual vmware users.
>
> On 12/15/2010 09:59 AM, brad hancock wrote:
>> We have never used RDM in the past due to backup reasons etc and VM
>> admins not having to deal the SAN admins. Do you think this would
>> resolve the issue?
>>  
>>
>>
>> On Tue, Dec 14, 2010 at 3:25 PM, Sunil Mushran
>> mailto:sunil.mush...@oracle.com>> wrote:
>>
>> I meant repeats 60 secs at a stretch. If not, as it seems so,
>> then the messages
>> should be only annoying.
>>
>> VMFS uses SCSI Reservation to perform disk based locking. See if
>> they have
>> some logging in ESX that shows when a VMFS performs reserve/unreserve
>> on a SCSI device. You'll have to look at the logs of all nodes.
>> As in, that log
>> will be on a different node than that that got this error.
>>
>> BTW, any reason you are not using RDM.
>>
>>
>> On 12/14/2010 12:51 PM, brad hancock wrote:
>>> The issue does repeat. 
>>>
>>> I looked through the vsphere 4.1, and the host logs and didn't
>>> see anything weird that corresponds with these times. 
>>>
>>> What is a reservation conflict? Can this issue cause the nodes
>>> to see different data?
>>>
>>>
>>> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113847] sd 1:0:0:0:
>>> reservation conflict
>>> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113859] sd 1:0:0:0:
>>> [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
>>> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113868] end_request:
>>> I/O error, dev sdb, sector 1735
>>> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114134]
>>> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
>>> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114379]
>>> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233764] sd 1:0:0:0:
>>> reservation conflict
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233775] sd 1:0:0:0:
>>> [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233855] end_request:
>>> I/O error, dev sdb, sector 1735
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234112]
>>> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234365]
>>> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234789] sd 1:0:0:0:
>>> reservation conflict
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234793] sd 1:0:0:0:
>>> [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234796] end_request:
>>> I/O error, dev sdb, sector 1735
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235033]
>>> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
>>> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235273]
>>> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
>>> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734356] sd 1:0:0:0:
>>> reservation conflict
>>> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734366] sd 1:0:0:0:
>>> [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
>>> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734370] end_request:
>>> I/O error, dev sdb, sector 1735
>>> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734620]
>>> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
>>> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734882]
>>> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
>>> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184302] sd 1:0:0:0:
>>> reservation conflict
>>> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184312] sd 1:0:0:0:
>>> [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
>>> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184316] end_request:
>>> I/O error, dev sdb, sector 1735
>>> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184565]
>>> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
>>> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184809]
>>> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5

Re: [Ocfs2-users] Reservation conflicts

[Sunil Mushran]

Ideally the scsi reservation error should be trapped by hypervisor/mgmt
domain and should not bubble upto the guest. That is if vmfs is doing the
reservation. Have you looked into the logs on all machines? See if there
is a way to get vmfs to log that info.

As far as RDM's goes, that's how I believe people use it. But you'll have to
get confirmation from actual vmware users.

On 12/15/2010 09:59 AM, brad hancock wrote:

We have never used RDM in the past due to backup reasons etc and VM admins not 
having to deal the SAN admins. Do you think this would resolve the issue?


On Tue, Dec 14, 2010 at 3:25 PM, Sunil Mushran mailto:sunil.mush...@oracle.com>> wrote:

I meant repeats 60 secs at a stretch. If not, as it seems so, then the 
messages
should be only annoying.

VMFS uses SCSI Reservation to perform disk based locking. See if they have
some logging in ESX that shows when a VMFS performs reserve/unreserve
on a SCSI device. You'll have to look at the logs of all nodes. As in, that 
log
will be on a different node than that that got this error.

BTW, any reason you are not using RDM.


On 12/14/2010 12:51 PM, brad hancock wrote:

The issue does repeat.

I looked through the vsphere 4.1, and the host logs and didn't see anything 
weird that corresponds with these times.

What is a reservation conflict? Can this issue cause the nodes to see 
different data?


Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113847] sd 1:0:0:0: reservation 
conflict
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113859] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113868] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114134] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114379] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233764] sd 1:0:0:0: reservation 
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233775] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233855] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234112] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234365] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234789] sd 1:0:0:0: reservation 
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234793] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234796] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235033] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235273] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734356] sd 1:0:0:0: reservation 
conflict
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734366] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734370] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734620] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734882] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184302] sd 1:0:0:0: reservation 
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184312] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184316] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184565] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184809] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: reservation 
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] 
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation 
conflict
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb] 
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error, 
dev sdb, sector 1735
Dec 14 10:33:08 mdcvmsme

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

We have never used RDM in the past due to backup reasons etc and VM admins
not having to deal the SAN admins. Do you think this would resolve the
issue?



On Tue, Dec 14, 2010 at 3:25 PM, Sunil Mushran wrote:

>  I meant repeats 60 secs at a stretch. If not, as it seems so, then the
> messages
> should be only annoying.
>
> VMFS uses SCSI Reservation to perform disk based locking. See if they have
> some logging in ESX that shows when a VMFS performs reserve/unreserve
> on a SCSI device. You'll have to look at the logs of all nodes. As in, that
> log
> will be on a different node than that that got this error.
>
> BTW, any reason you are not using RDM.
>
>
> On 12/14/2010 12:51 PM, brad hancock wrote:
>
> The issue does repeat.
>
>  I looked through the vsphere 4.1, and the host logs and didn't see
> anything weird that corresponds with these times.
>
>  What is a reservation conflict? Can this issue cause the nodes to see
> different data?
>
>
>  Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113847] sd 1:0:0:0:
> reservation conflict
> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113859] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113868] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114134]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114379]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233764] sd 1:0:0:0: reservation
> conflict
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233775] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233855] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234112]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234365]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234789] sd 1:0:0:0: reservation
> conflict
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234793] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234796] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235033]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235273]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734356] sd 1:0:0:0: reservation
> conflict
> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734366] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734370] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734620]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734882]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184302] sd 1:0:0:0: reservation
> conflict
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184312] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184316] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184565]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184809]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: reservation
> conflict
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation
> conflict
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error,
> dev sdb, sector 1735
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
> (0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
> (1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation
> conflict
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
> Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error,
> dev sdb, sector

Re: [Ocfs2-users] Reservation conflicts

[Sunil Mushran]

I meant repeats 60 secs at a stretch. If not, as it seems so, then the messages
should be only annoying.

VMFS uses SCSI Reservation to perform disk based locking. See if they have
some logging in ESX that shows when a VMFS performs reserve/unreserve
on a SCSI device. You'll have to look at the logs of all nodes. As in, that log
will be on a different node than that that got this error.

BTW, any reason you are not using RDM.

On 12/14/2010 12:51 PM, brad hancock wrote:

The issue does repeat.

I looked through the vsphere 4.1, and the host logs and didn't see anything 
weird that corresponds with these times.

What is a reservation conflict? Can this issue cause the nodes to see different 
data?


Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113847] sd 1:0:0:0: reservation 
conflict
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113859] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113868] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114134] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114379] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233764] sd 1:0:0:0: reservation 
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233775] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233855] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234112] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234365] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234789] sd 1:0:0:0: reservation 
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234793] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234796] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235033] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235273] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734356] sd 1:0:0:0: reservation 
conflict
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734366] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734370] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734620] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734882] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184302] sd 1:0:0:0: reservation 
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184312] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184316] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184565] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184809] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: reservation 
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation 
conflict
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation 
conflict
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error, dev 
sdb, sector 1735
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] (0,0):o2hb_bio_end_io:225 
ERROR: IO Error -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] 
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5







On Tue, Dec 14, 2010 at 11:38 AM, Sunil Mushran mailto:sunil.mush...@oracle.com>> wrote:

sd 1:0:0:0: reservation conflict

That's the caus

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

The issue does repeat.

I looked through the vsphere 4.1, and the host logs and didn't see anything
weird that corresponds with these times.

What is a reservation conflict? Can this issue cause the nodes to see
different data?


Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113847] sd 1:0:0:0: reservation
conflict
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113859] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.113868] end_request: I/O error,
dev sdb, sector 1735
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114134]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:37:52 mdcvmsmes02 kernel: [351952.114379]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233764] sd 1:0:0:0: reservation
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233775] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.233855] end_request: I/O error,
dev sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234112]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234365]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234789] sd 1:0:0:0: reservation
conflict
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234793] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.234796] end_request: I/O error,
dev sdb, sector 1735
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235033]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 07:51:01 mdcvmsmes02 kernel: [352762.235273]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734356] sd 1:0:0:0: reservation
conflict
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734366] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734370] end_request: I/O error,
dev sdb, sector 1735
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734620]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 09:23:15 mdcvmsmes02 kernel: [358423.734882]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184302] sd 1:0:0:0: reservation
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184312] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184316] end_request: I/O error,
dev sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184565]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.184809]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: reservation
conflict
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045] end_request: I/O error,
dev sdb, sector 1735
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:25:27 mdcvmsmes02 kernel: [362254.188045]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation
conflict
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error,
dev sdb, sector 1735
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: reservation
conflict
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] sd 1:0:0:0: [sdb]
Result: hostbyte=DID_OK driverbyte=DRIVER_OK,SUGGEST_OK
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062] end_request: I/O error,
dev sdb, sector 1735
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
(0,0):o2hb_bio_end_io:225 ERROR: IO Error -5
Dec 14 10:33:08 mdcvmsmes02 kernel: [362727.621062]
(1882,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5







On Tue, Dec 14, 2010 at 11:38 AM, Sunil Mushran wrote:

>  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

Re: [Ocfs2-users] Reservation conflicts

[Sunil Mushran]

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 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, mailto:ke...@utahsysadmin.com>> wrote:

On Fri, 10 Dec 2010 06:26:06 -0800, 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

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

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 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,  wrote:
>
>> On Fri, 10 Dec 2010 06:26:06 -0800, 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

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

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,  wrote:

> On Fri, 10 Dec 2010 06:26:06 -0800, 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

Re: [Ocfs2-users] Reservation conflicts

[kevin]

On Fri, 10 Dec 2010 06:26:06 -0800, 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

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

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.






On Thu, Dec 9, 2010 at 5:29 PM, Ulf Zimmermann  wrote:
>
> > -Original Message-
> > From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-
> > boun...@oss.oracle.com] On Behalf Of Joel Becker
> > Sent: Thursday, December 09, 2010 2:54 PM
> > To: brad hancock
> > Cc: ocfs2-users@oss.oracle.com
> > Subject: Re: [Ocfs2-users] Reservation conflicts
> >
> > On Thu, Dec 09, 2010 at 04:45:25PM -0600, brad hancock wrote:
> > > Yeah both guest have the same Harddrive attached with the virtual
> > scsi
> > > controller configured
> > > as Physical to set a  policy to allow virtual disk to be
> > > used simultaneously by multi virtual machines.
> > >
> > > as /dev/sdb1
> >
> >   It sure seems like VMWare is caching some data somewhere.
> > That's my best guess.  These are on the same host, right?
> >
> > Joel
>
> I have configured:
>
> SCSI Controller 1 Virtual (Virtual disks can be shared between any virtual
> machines on the same server.)
> Disks are configured as Independent.
>
> That works for my test cluster using OCFS inside of Vmware.
>
>
___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Re: [Ocfs2-users] Reservation conflicts

[Ulf Zimmermann]

> -Original Message-
> From: ocfs2-users-boun...@oss.oracle.com [mailto:ocfs2-users-
> boun...@oss.oracle.com] On Behalf Of Joel Becker
> Sent: Thursday, December 09, 2010 2:54 PM
> To: brad hancock
> Cc: ocfs2-users@oss.oracle.com
> Subject: Re: [Ocfs2-users] Reservation conflicts
> 
> On Thu, Dec 09, 2010 at 04:45:25PM -0600, brad hancock wrote:
> > Yeah both guest have the same Harddrive attached with the virtual
> scsi
> > controller configured
> > as Physical to set a  policy to allow virtual disk to be
> > used simultaneously by multi virtual machines.
> >
> > as /dev/sdb1
> 
>   It sure seems like VMWare is caching some data somewhere.
> That's my best guess.  These are on the same host, right?
> 
> Joel

I have configured:

SCSI Controller 1 Virtual (Virtual disks can be shared between any virtual 
machines on the same server.)
Disks are configured as Independent.

That works for my test cluster using OCFS inside of Vmware.


___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Re: [Ocfs2-users] Reservation conflicts

[Joel Becker]

On Thu, Dec 09, 2010 at 04:45:25PM -0600, brad hancock wrote:
> Yeah both guest have the same Harddrive attached with the virtual scsi
> controller configured
> as Physical to set a  policy to allow virtual disk to be
> used simultaneously by multi virtual machines.
> 
> as /dev/sdb1

It sure seems like VMWare is caching some data somewhere.
That's my best guess.  These are on the same host, right?

Joel

-- 

Life's Little Instruction Book #510

"Count your blessings."

Joel Becker
Senior Development Manager
Oracle
E-mail: joel.bec...@oracle.com
Phone: (650) 506-8127

___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Re: [Ocfs2-users] Reservation conflicts

[brad hancock]

Yeah both guest have the same Harddrive attached with the virtual scsi
controller configured
as Physical to set a  policy to allow virtual disk to be
used simultaneously by multi virtual machines.

as /dev/sdb1

node:
ip_port = 
ip_address = 10.0.0.1
number = 0
name = mdcvmsmes01
cluster = ocfs2

node:
ip_port = 
ip_address = 10.0.0.2
number = 1
name = mdcvmsmes02
cluster = ocfs2

cluster:
node_count = 2
name = ocfs2

On Thu, Dec 9, 2010 at 4:15 PM, Joel Becker  wrote:

> On Thu, Dec 09, 2010 at 04:02:14PM -0600, brad hancock wrote:
> > I have two vmware guests that share a OCFS2 partition through VMWare
> VMFS.
> > It resides on a SAN.
>
> Let me see if I understand the configuration.  You have a SAN.
> On that SAN is a LUN.  You have one VMWare host in this configuration.
> The VMWare host has formatted that LUN for VMFS.  There is a disk image
> on the VMFS that both guests see as sdb.  Is this correct?
>
> > Each host has the following error in the kernel log:
> >
> > [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
> >
> >
> > We also see the following on both machines:
> >
> >  (1888,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> > [202381.822030] (1888,0):o2hb_do_disk_heartbeat:762 ERROR: Device "sdb1":
> > another node is heartbeating in our slot!
> >
> > I notice the sector is the same on both machines: 1735.
> >
> > Is this an issue with vmware?
>
> The read errors ("another node is heartbeating in our slot")
> sound like VMWare is not allowing the nodes to see each other's
> activity.  The write error is more surprising, but it could be part of
> the same issue.
>
> Joel
>
>
> --
>
> "Every day I get up and look through the Forbes list of the richest
>  people in America. If I'm not there, I go to work."
>- Robert Orben
>
> Joel Becker
> Senior Development Manager
> Oracle
> E-mail: joel.bec...@oracle.com
> Phone: (650) 506-8127
>
___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

Re: [Ocfs2-users] Reservation conflicts

[Joel Becker]

On Thu, Dec 09, 2010 at 04:02:14PM -0600, brad hancock wrote:
> I have two vmware guests that share a OCFS2 partition through VMWare VMFS.
> It resides on a SAN.

Let me see if I understand the configuration.  You have a SAN.
On that SAN is a LUN.  You have one VMWare host in this configuration.
The VMWare host has formatted that LUN for VMFS.  There is a disk image
on the VMFS that both guests see as sdb.  Is this correct?

> Each host has the following error in the kernel log:
> 
> [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
> 
> 
> We also see the following on both machines:
> 
>  (1888,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
> [202381.822030] (1888,0):o2hb_do_disk_heartbeat:762 ERROR: Device "sdb1":
> another node is heartbeating in our slot!
> 
> I notice the sector is the same on both machines: 1735.
> 
> Is this an issue with vmware?

The read errors ("another node is heartbeating in our slot")
sound like VMWare is not allowing the nodes to see each other's
activity.  The write error is more surprising, but it could be part of
the same issue.

Joel


-- 

"Every day I get up and look through the Forbes list of the richest
 people in America. If I'm not there, I go to work."
- Robert Orben

Joel Becker
Senior Development Manager
Oracle
E-mail: joel.bec...@oracle.com
Phone: (650) 506-8127

___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users

[Ocfs2-users] Reservation conflicts

[brad hancock]

I have two vmware guests that share a OCFS2 partition through VMWare VMFS.
It resides on a SAN.

Each host has the following error in the kernel log:

[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


We also see the following on both machines:

 (1888,0):o2hb_do_disk_heartbeat:753 ERROR: status = -5
[202381.822030] (1888,0):o2hb_do_disk_heartbeat:762 ERROR: Device "sdb1":
another node is heartbeating in our slot!

I notice the sector is the same on both machines: 1735.

Is this an issue with vmware?

thanks,
___
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users