vmware ESX3.5 の  RESERVATION CONFLICT

vmware ESX3.5 RESERVATION CONFLICTでiSCSIデータストレージにアクセス出来なくなる。

Vmware Infrastructure Client の構成>ストレージアダプタ から iSCSI Software Adapterであるvmhba32の詳細を見ると容量のところが通常2.0TBとか出るはずのところが0になってしまっている。

現在BuffaloのTera Station ProというVmware製品が非サポートのストレージを使用しているため、自力復旧を試みる。

■ESX3.5にssh接続してdmesg見てみると、

scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
sdb : READ CAPACITY failed.
status = c, message = 00, host = 0, driver = 00
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
VMWARE: Device that would have been attached as scsi disk sdb at scsi3, channel 0, id 0, lun 0
Has not been attached because this path could not complete a READ command eventhough a TUR worked.
result = 0x18 key = 0x0, asc = 0x0, ascq = 0x0
VMWARE: Device that would have been attached as scsi disk sdb at scsi3, channel 0, id 0, lun 0
Has not been attached because it is a duplicate path or on a passive path
scan_scsis starting finish
scan_scsis done with finish
scsi singledevice 3 0 0 0
Vendor: BUFFALO Model: VIRTUAL-DISK Rev: 0
Type: Direct-Access ANSI SCSI revision: 04
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
sdb : READ CAPACITY failed.
status = c, message = 00, host = 0, driver = 00
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
scsi3 (0,0,0) : RESERVATION CONFLICT
VMWARE: Device that would have been attached as scsi disk sdb at scsi3, channel 0, id 0, lun 0
Has not been attached because this path could not complete a READ command eventhough a TUR worked.
result = 0x18 key = 0x0, asc = 0x0, ascq = 0x0
VMWARE: Device that would have been attached as scsi disk sdb at scsi3, channel 0, id 0, lun 0
Has not been attached because it is a duplicate path or on a passive path

■cat /var/log/vmkwarning すると、下記のようなメッセージがある。
Aug 10 19:17:00 esx7 vmkernel: 0:00:43:11.077 cpu3:1037)WARNING: SCSI: 119: Failing I/O due to too many reservation conflicts
Aug 10 19:17:00 esx7 vmkernel: 0:00:43:11.077 cpu3:1037)WARNING: ScsiDevice: 3362: Failed for vml.010000000012345678901234567890: SCSI reservation conflict


■英語だとあちこちにヒントが
例えばここ。
http://blog.michaelfmcnamara.com/2009/09/vsphere-scsi-reserv-co/

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002293#esx35




vmkfstools -L lunreset /vmfs/devices/disks/vml.010000000020202020564952545541
とか
esxcfg-info | egrep -B5 "s Reserved|Pending"
とか 
色々試してみました。

しかし、結局解決に結びつかず。


試行錯誤の結果今のところは、
「パスの管理」より、

ラウンドロビン(試験的)」 を選択することで回避している。


依然としてヒヤヒヤ感は拭えないわけだが。。。