ZFS Snapshot replication and esxi 6.0 storage mounting.

[Aldino76]

Hello to everyone,

I hope someone could help me in this issue that stole to me a lot of time during past weeks.

I Have two Freenas identical boxes;

The first one called ALPHA (freeness 9.3) has a ZFS pool and it is the main storage.
I'm exporting with it 2 different ZVol with ISCSI protocol, for 2 esxi 6.0 hosts.
On those Luns there are about 4 VM perfectly running on remote hosts.

The second one called BETA (freeness 9.10) is empty.
I've obiuvsly created a ZFS pool from scratch, and all seems to be fine.

I've then set up a snapshot task replication from ALPHA (push system) to BETA (pull system),
and the process work like a charm. I can see full gigabit ethernet bandwidth during sync process and
no problem at all.
I see that synchronization running fine and finally I can see the up to date status on the primary side (ALPHA) and all volumes replicated in Storage section of BETA system.

All seems to be fine, and correctly replicated on the remote side.

The problem start here:

I try to export replicated ZVol on an esxi host, configuring ISCSI portal and targets.
The ISCSI configuration is correct. No doubt about it.

Well, the I try to mount on esxi 6.0 host the exported luns, I can't see in storage devices the devices.
They are correctly recognised, but I can't mount devices (I've choosed the "keep existing signature" option).
I've controlled all device properties and I saw that those devices are all in read only mode on BETA side.

I've searched on the forum and googled for weeks, but I've found poor posts with no solutions...
I tried everything: I've cloned snapshot, tried to rollback it, I've tried to destroy and do all steps from the beginning.
I've tried also to install on BETA freeness 9.3 to have perfect alignment of versions.

NOTHING.

Same issue, always same problem: No way to mount those replicated devices
I've created a new Zvol from scratch on BETA and successfully exported it by ISCSI.
In this case I can mount on esxi side the storage, and all work fine...

Can someone help me and tell me in what I'm wrong??

Thanks in advance

A.

P.S.

I add an information:
on the eventVsphere log (esxi side, ), I can see this error when I try to mount the lun:
"Login to ISCSI Target iqn....... failed. The ISCSI initiator could not establish anetwork connection to the target."

Seems to be a network problem, but i think it's not.
Obiuvsly i've googled a lot, but no real solution found.

 

[depasseg]

IIRC it has something to do with disk signatures.
https://forums.freenas.org/index.ph...ol-snapshots-through-iscsi.42411/#post-275091
https://kb.vmware.com/selfservice/m...nguage=en_US&cmd=displayKC&externalId=1011387

 

[Aldino76]

IIRC it has something to do with disk signatures.
https://forums.freenas.org/index.ph...ol-snapshots-through-iscsi.42411/#post-275091
https://kb.vmware.com/selfservice/m...nguage=en_US&cmd=displayKC&externalId=1011387

Thank you depasseg,

Those are not my cases and I have not those symptoms.
In fact, I try to mount on a third blank and fresh installed machine (esxi 6.0 host update2).

I add an information:
on the event log (esxi side), I can see this error when I try to mount the lun:

"Login to ISCSI Target iqn....... failed. The ISCSI initiator could not establish anetwork connection to the target."

Seems to be a network problem, but i think it's not.

 

[jgreco]

It's not clear to me why this would be a "network problem." As long as the initiator and target can ping each other, and I hope you've checked with vmkping, it's exceedingly unlikely to be a "network problem."

What's the FreeNAS side saying as to what's going on? Problems could range from you forgot to turn on iSCSI all the way on up to esoteric authentication and configuration issues.

 

[Aldino76]

It's not clear to me why this would be a "network problem." As long as the initiator and target can ping each other, and I hope you've checked with vmkping, it's exceedingly unlikely to be a "network problem."

What's the FreeNAS side saying as to what's going on? Problems could range from you forgot to turn on iSCSI all the way on up to esoteric authentication and configuration issues.

Thank you for your answer,

I confirm that I can ping hosts each other and network traffic is perfect.
The ISCSI configuration is really basic, without any authentication or other limitation....

 

[jgreco]

Okay, well, that doesn't really tell me much of anything. The problem here is that you're the eyes and ears, and I can only make educated guesses as to what might be going on, so the more information you can provide, the better it is.

It sounds like the device isn't being mounted, so you should probably tackle it from that angle. I don't actually use ZFS replication for backups so I'm only kinda guessing that maybe the snapshot should be cloned, which would give you something that you can read and write, and then you could try mounting that.

 

[Aldino76]

Okay, well, that doesn't really tell me much of anything. The problem here is that you're the eyes and ears, and I can only make educated guesses as to what might be going on, so the more information you can provide, the better it is.

It sounds like the device isn't being mounted, so you should probably tackle it from that angle. I don't actually use ZFS replication for backups so I'm only kinda guessing that maybe the snapshot should be cloned, which would give you something that you can read and write, and then you could try mounting that.

Sure, I've tried to clone and mounting the clone, but no luck...
It's really a challenging situation....

 

[UdoB]

Same issue, always same problem: No way to mount those replicated devices

Please check the "readonly" property (zfs get readonly tank/backupdataset) on the destination system. Perhaps it is "on" due to the replication process.

Best regards

 

[Aldino76]

Please check the "readonly" property (zfs get readonly tank/backupdataset) on the destination system. Perhaps it is "on" due to the replication process.

Best regards

Thank you UdoB,

yes the target is readonly, but the problem is the i don't know how to mount the Zvol...

 

[Aldino76]

Hello Sirs,

Is there anybody that can help me?
I really don't know what to do....

 

[depasseg]

So to summarize-- you can successfully mount a fresh zvol ISCSI target on Beta, but you cannot mount the replicated zvol on Beta and you don't think it has anything to do with the disk signature on the replcated zvol. Is that an accurate assessment of the situation?

 

[Aldino76]

So to summarize-- you can successfully mount a fresh zvol ISCSI target on Beta, but you cannot mount the replicated zvol on Beta and you don't think it has anything to do with the disk signature on the replcated zvol. Is that an accurate assessment of the situation?

Yes sure. This is the situation.

 

[Aldino76]

Little update:
on essi 6.0 side, whet I try to mount the replicated Zvol, the tail-f /var/log/vmkernel.log is:

Code:

016-06-21T15:25:30.434Z cpu4:33155)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x89 (0x43a18038e340, 34154) to dev "naa.6589cfc00000075abbde0117d114aaf1" on path "vmhba36:C1:T1:L10" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x7 0x27 0x1. Act:NONE

2016-06-21T15:25:30.434Z cpu4:33155)ScsiDeviceIO: 2651: Cmd(0x43a18038e340) 0x89, CmdSN 0x2 from world 34154 to dev "naa.6589cfc00000075abbde0117d114aaf1" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x7 0x27 0x1.

2016-06-21T15:25:30.434Z cpu5:34154 opID=e750db65)World: 15516: VC opID BA25D173-000002BE-87bc maps to vmkernel opID e750db65

2016-06-21T15:25:30.434Z cpu5:34154 opID=e750db65)LVM: 6112: Forcing APD unregistration of devID 56d71e8a-f4bc5a02-4051-001f2956d0fe in state 1.

2016-06-21T15:25:30.434Z cpu5:34154 opID=e750db65)LVM: 13750: Failed to open device naa.6589cfc00000075abbde0117d114aaf1:1 : Read only

2016-06-21T15:25:30.436Z cpu6:32797)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a180351e40, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.440Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.440Z cpu6:32797)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a180351e40, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.443Z cpu6:32797)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x43a180351e40, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.455Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.464Z cpu5:34154 opID=e750db65)LVM: 10080: Device naa.6589cfc00000075abbde0117d114aaf1:1 detected to be a snapshot:

2016-06-21T15:25:30.464Z cpu5:34154 opID=e750db65)LVM: 10087:   queried disk ID: <type 1, len 22, lun 10, devType 0, scsi 0, h(id) 11785045161014366340>

2016-06-21T15:25:30.464Z cpu5:34154 opID=e750db65)LVM: 10094:   on-disk disk ID: <type 1, len 20, lun 1, devType 0, scsi 0, h(id) 15344552743697335650>

2016-06-21T15:25:30.475Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.475Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a185f7c400, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.476Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.476Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a185f7c400, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.477Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.477Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a185f7c400, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.479Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.479Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a185f7c400, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.481Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.481Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3248: last error status from device mpx.vmhba0:C0:T0:L0 repeated 1 times

2016-06-21T15:25:30.481Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a1802e3e00, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.482Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.482Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a1802e3e00, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.484Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.484Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3248: last error status from device mpx.vmhba0:C0:T0:L0 repeated 1 times

2016-06-21T15:25:30.484Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a180382800, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.485Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.486Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a180382800, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.487Z cpu5:34154 opID=e750db65)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12

2016-06-21T15:25:30.487Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a180382800, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:30.488Z cpu5:34154 opID=e750db65)FSS: 5334: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': No filesystem on the device

2016-06-21T15:25:30.498Z cpu7:32798)NMP: nmp_ThrottleLogForDevice:3231: last error status from device mpx.vmhba32:C0:T0:L0 repeated 10 times

2016-06-21T15:25:30.562Z cpu5:34154 opID=e750db65)VC: 3551: Device rescan time 33 msec (total number of devices 5)

2016-06-21T15:25:30.562Z cpu5:34154 opID=e750db65)VC: 3554: Filesystem probe time 93 msec (devices probed 5 of 5)

2016-06-21T15:25:30.562Z cpu5:34154 opID=e750db65)VC: 3556: Refresh open volume time 0 msec

2016-06-21T15:25:30.939Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x43a1802e8100, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:25:30.942Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x43a1802e8100, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:25:58.264Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a187315000, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:58.281Z cpu4:33045)<4>hpsa 0000:03:00.0: Device:C3:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.

2016-06-21T15:25:58.281Z cpu5:32874)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x85 (0x43a187315000, 34328) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:25:58.281Z cpu5:32874)ScsiDeviceIO: 2635: Cmd(0x43a187315000) 0x85, CmdSN 0x786 from world 34328 to dev "naa.600508b1001c1d0293d689fcb612c3ac" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2016-06-21T15:25:58.292Z cpu5:32779)ScsiDeviceIO: 2651: Cmd(0x43a187315000) 0x4d, CmdSN 0x787 from world 34328 to dev "naa.600508b1001c1d0293d689fcb612c3ac" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2016-06-21T15:25:58.292Z cpu5:32779)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x43a187315000, 34328) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:25:58.292Z cpu5:32779)ScsiDeviceIO: 2651: Cmd(0x43a187315000) 0x1a, CmdSN 0x788 from world 34328 to dev "naa.600508b1001c1d0293d689fcb612c3ac" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2016-06-21T15:25:58.303Z cpu4:33046)<4>hpsa 0000:03:00.0: Device:C3:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.

2016-06-21T15:25:58.303Z cpu5:32779)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x85 (0x43a187315000, 34328) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:26:58.073Z cpu4:33165)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device mpx.vmhba32:C0:T0:L0 repeated 1 times

2016-06-21T15:29:28.076Z cpu7:567446)ScsiScan: 836: Path vmhba36:C1:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:29:28.077Z cpu7:567446)ScsiScan: 836: Path vmhba36:C2:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:29:28.079Z cpu6:32874)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x43a18030b6c0, 0) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:29:28.080Z cpu4:32795)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x43a18030b6c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:33:58.536Z cpu5:32796)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x9e (0x43a18030b6c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:34:28.079Z cpu5:567088)ScsiScan: 836: Path vmhba36:C1:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:34:28.080Z cpu5:567088)ScsiScan: 836: Path vmhba36:C2:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:34:28.081Z cpu1:32949)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d803715c0, 0) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:34:28.082Z cpu1:32792)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x439d803715c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:34:58.078Z cpu0:33165)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device mpx.vmhba32:C0:T0:L0 repeated 2 times

2016-06-21T15:39:28.085Z cpu6:32933)ScsiScan: 836: Path vmhba36:C1:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:39:28.086Z cpu6:32933)ScsiScan: 836: Path vmhba36:C2:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:39:28.087Z cpu0:32828)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d88b55480, 0) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:39:28.089Z cpu0:32791)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x439d88b55480, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:44:28.089Z cpu4:568629)ScsiScan: 836: Path vmhba36:C1:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:44:28.091Z cpu4:568629)ScsiScan: 836: Path vmhba36:C2:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:44:28.092Z cpu1:32953)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x439d88b55480, 0) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:44:28.093Z cpu1:32792)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x439d88b55480, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-06-21T15:49:28.094Z cpu0:569524)ScsiScan: 836: Path vmhba36:C1:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:49:28.107Z cpu0:569524)ScsiScan: 836: Path vmhba36:C2:T1:L0 supports REPORT LUNS 0x11

2016-06-21T15:49:28.107Z cpu5:33046)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x12 (0x43a187314700, 0) to dev "naa.600508b1001c1d0293d689fcb612c3ac" on path "vmhba1:C0:T0:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0. Act:NONE

2016-06-21T15:49:28.108Z cpu7:32798)NMP: nmp_ThrottleLogForDevice:3298: Cmd 0x1a (0x43a187314700, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

 

[Mirfster]

Wrapping tons of text in CODE Tags helps keep the forums from crying... ;)

 

[jgreco]

Wrapping tons of text in CODE Tags helps keep the forums from crying... ;)

mod note: Fixored, at least partially. Didn't feel like re-editing the double line feeds.

 

[depasseg]

Your error messages look eerily similar to the messages in the vmware KB article I posted above.

 

[jgreco]

Your error messages look eerily similar to the messages in the vmware KB article I posted above.
View attachment 12342

I have to agree. I don't really work with snapshots like this but it seems the most likely answer, as the host obviously sees the target and is being cautious because of the snapshot/signature/etc. The resolution suggested in the VMware KB seems like it'd be the thing to try.