Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

Esx sees deleted RDM lun paths

$
0
0

Hi ,

I have created a RDM lun on windows 2k3 GOS, esx 3.02, using FCP emulex hba and again deleted.

RDM got deleted from GOS but ESX is still seeing it.

 

esxcfg-mpath -l shows these deleted LUN.

 

Disk vmhba5:3:6  (3074MB) has 1 paths and policy of Fixed

FC 8:1.0 10000000c948cb98<->500a09818534c06e vmhba5:3:6 On active preferred

 

Disk vmhba5:6:6  (3074MB) has 1 paths and policy of Fixed

FC 8:1.0 10000000c948cb98<->500a09898534c06e vmhba5:6:6 On active preferred

 

But esxcfg-vmhbadevs does not show device.

 

vmhba0:128:0        /dev/sda

vmhba5:3:0          /dev/sdb

vmhba5:3:1          /dev/sdc

vmhba5:3:2          /dev/sdd

vmhba5:3:3          /dev/sde

vmhba5:3:4          /dev/sdf

vmhba5:6:4

vmhba5:3:5          /dev/sdg

vmhba5:3:6

vmhba5:6:6

 

Even rescan doesnt remove the paths.

vmkwarning shows these errors:

 

Jul 18 23:39:20 esx-225-150 vmkernel: 0:05:26:49.473 cpu1:1036)WARNING: SCSI: 6325: Failed for vmhba5:3:6: I/O error

Jul 18 23:39:20 esx-225-150 vmkernel: 0:05:26:49.491 cpu1:1036)WARNING: SCSI: 7917: status I/O error, rstatus #c0de00 for vmhba5:6:6. residual R 999, CR 80, ER 3

Jul 18 23:39:20 esx-225-150 vmkernel: 0:05:26:49.491 cpu1:1036)WARNING: SCSI: 6325: Failed for vmhba5:6:6: I/O error

Jul 18 23:39:21 esx-225-150 vmkernel: 0:05:26:50.329 cpu0:1042)WARNING: SCSI: 1736: Unexpected status returned: bad000a I/O error

Jul 18 23:39:21 esx-225-150 vmkernel: 0:05:26:50.347 cpu0:1042)WARNING: SCSI: 1736: Unexpected status returned: bad000a I/O error

Jul 18 23:39:28 esx-225-150 vmkernel: 0:05:26:57.656 cpu1:1035)WARNING: SCSI: 2215: Cannot remove target. World 1062 has not completely released the device.

Jul 18 23:39:28 esx-225-150 vmkernel: 0:05:26:57.656 cpu1:1035)WARNING: LinSCSI: 4591: The physical media represented by vmhba5:3:4 has changed and the device is in use. The device cannot be re-synchronized with the system. This is a critical error.

Jul 18 23:39:28 esx-225-150 vmkernel: 0:05:26:57.657 cpu1:1035)WARNING: SCSI: 2215: Cannot remove target. World 1062 has not completely released the device.

Jul 18 23:39:28 esx-225-150 vmkernel: 0:05:26:57.657 cpu1:1035)WARNING: LinSCSI: 4613: Device vmhba5:3:6 has disappeared but is currently in use and could not be removed.

Jul 18 23:39:36 esx-225-150 vmkernel: 0:05:27:04.849 cpu1:1035)WARNING: SCSI: 2215: Cannot remove target. World 1062 has not completely released the device.

Jul 18 23:39:36 esx-225-150 vmkernel: 0:05:27:04.849 cpu1:1035)WARNING: LinSCSI: 4591: The physical media represented by vmhba5:6:4 has changed and the device is in use. The device cannot be re-synchronized with the system. This is a critical error.

Jul 18 23:39:36 esx-225-150 vmkernel: 0:05:27:04.851 cpu1:1035)WARNING: SCSI: 2215: Cannot remove target. World 1062 has not completely released the device.

Jul 18 23:39:36 esx-225-150 vmkernel: 0:05:27:04.851 cpu1:1035)WARNING: LinSCSI: 4613: Device vmhba5:6:6 has disappeared but is currently in use and could not be removed.

Jul 18 23:39:38 esx-225-150 vmkernel: 0:05:27:07.540 cpu1:1035)WARNING: SCSI: 7917: status I/O error, rstatus #c0de00 for vmhba5:3:6. residual R 999, CR 80, ER 3

 

hostd dont show any errors.

 

Any idea why esx still sees this lun ?

 

Thanks,

Tapesh.


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>