Re: unmount datastore without deleting VM-s

istvankope · ‎01-06-2018

Hello,

I messed up the datastore resize and now I get a "read only" error when I try the resize again. I found this topic and I want get a new signature for the datastore by unmounting and re-adding it.

vmkfstools --growfs returning Error: No such file or directory

The problem is that this is a backup server and I have a VM with 18TB of data on it. I don't have time and disk space to backup this VM.

Please tell me if there is a possibility to unmount the datastore and re-add it to obtain a new signature without losing the VM on it?

Or is there a possibility to reduce the size of the datastore?

Istvan

daphnissov · ‎01-06-2018

AFAIK, there's no way to resignature a VMFS volume that is not detected as a snapshot, and for that to occur it has to have seen the same VMFS signature more than once. So in your case, you may need to migrate the data and reformat the VMFS volume.

------------------
How to Ask for Help on Tech Forums
https://neonmirrors.net

istvankope · ‎01-06-2018

Can you tell me if this problem can be solved with an utility like a bootable Acronis Disk Director or something similar?

daphnissov · ‎01-06-2018

I'm not really clear on your problem you say

I messed up the datastore resize and now I get a "read only" error when I try the resize again.

but what did you do in the first place? What is it you're trying to do here? Feel free to show some screenshots to illustrate what you have in your environment and how its configured.

------------------
How to Ask for Help on Tech Forums
https://neonmirrors.net

istvankope · ‎01-06-2018

I followed these instructions: VMware Knowledge Base

At this command:

# partedUtil resize "/vmfs/devices/disks/Device" PartitionNumber NewStartingSector NewEndingSector

For the NewEndingSector I didn't use "NewEndingSector-1" , I used the last sector. From here the vmkfstools --growfs "/vmfs/devices/disks/Device:partition" "/vmfs/devices/disks/Device:partition" command didn't work. My datastore is not resized. And I'm stuck here.

a_p_ · ‎01-06-2018

Not sure whether I can help. Anyway, please provide the output for the following three commands.

partedUtil get "/vmfs/devices/disks/<your-disk>"
partedUtil getptbl "/vmfs/devices/disks/<your-disk>"
partedUtil getUsableSectors "/vmfs/devices/disks/<your-disk>"

André

istvankope · ‎01-06-2018

Here you go Andre:

partedUtil get /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696

3404331 255 63 54690578432

1 64 8191 0 128

5 8224 520191 0 0

6 520224 1032191 0 0

7 1032224 1257471 0 0

8 1257504 1843199 0 0

2 1843200 10229759 0 0

3 10229760 54690578398 0 0

===========================================================================

partedUtil getptbl /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696

gpt

3404331 255 63 54690578432

1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

2 1843200 10229759 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

3 10229760 54690578398 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

===========================================================================

partedUtil getUsableSectors /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696

34 54690578398

a_p_ · ‎01-07-2018

To me this basically doesn't look incorrect, so I can't really tell you what to do at this point.

Some thoughts though:

What was the logical disk size (assuming that this is a RAID volume) before?
Did you check whether the RAID controller, and its drivers fully support the new volume size?

André

istvankope · ‎01-07-2018

As far as I read on the internet the 3rd partition's last sector supposed to be 54690578397, not 54690578398. This was my mistake.

Now the datastore is VMFS-5 18.2T 16.3T 1.9T 90% /vmfs/volumes/datastore1

It supposed to be somewhere around 25TB.

I assume if the RAID controller supports 18TB, it should not have problems with 25TB.

Before the resize it looked like this:

partedUtil get /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696

3404331 255 63 54690578432

1 64 8191 0 128

5 8224 520191 0 0

6 520224 1032191 0 0

7 1032224 1257471 0 0

8 1257504 1843199 0 0

2 1843200 10229759 0 0

3 10229760 39064698846 0 0

a_p_ · ‎01-07-2018

As far as I read on the internet the 3rd partition's last sector supposed to be 54690578397, not 54690578398 ...

According to the KB article (and from several times I resized partitions this way) the end sector seems to be ok. IMO the disk size minus 1 part is misleading anyway, and what should be used instead is the output of the partedUtil getUsableSectors command.

from the article:

subtract 1 from the disk size in sectors as reported in step 5 to obtain the last usable sector or use partedUtil getUsableSectors to get the last usable sector.

How did you proceed after the resize command? Did you follow the steps in the article, especially steps 9 (fixGpt), and 12 (refresh)?

André

istvankope · ‎01-07-2018

Everything went smooth until step 13 where I got this:

vmkfstools --growfs /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696:3 /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696:3

Not found

Error: No such file or directory

At step 12. vmkfstools -V didn't return any result. I even rebooted the server and repeated step 12-13, but had the same result.

Well if the last sector is ok, than I don't know where can be the problem. I even tried to repeat the resize from the WebUI but it says: No devices with free space.

Istvan

a_p_ · ‎01-07-2018

What's the output of

ls -lisa /vmfs/devices/disks/

Maybe this will help understanding what's wrong.

André

istvankope · ‎01-07-2018

ls -lisa /vmfs/devices/disks/

total 54690578321

4 0 drwxr-xr-x 2 root root 512 Jan 7 18:47 .

1 0 drwxr-xr-x 13 root root 512 Jan 7 18:47 ..

148 27345289216 -rw------- 1 root root 28001576157184 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696

134 4064 -rw------- 1 root root 4161536 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:1

136 4193280 -rw------- 1 root root 4293918720 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:2

138 27340174319 -rw------- 1 root root 27996338503168 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:3

140 255984 -rw------- 1 root root 262127616 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:5

142 255984 -rw------- 1 root root 262127616 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:6

144 112624 -rw------- 1 root root 115326976 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:7

146 292848 -rw------- 1 root root 299876352 Jan 7 18:47 naa.6782bcb04cd61a00ff00005004f68696:8

149 0 lrwxrwxrwx 1 root root 36 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048 -> naa.6782bcb04cd61a00ff00005004f68696

135 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:1 -> naa.6782bcb04cd61a00ff00005004f68696:1

137 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:2 -> naa.6782bcb04cd61a00ff00005004f68696:2

139 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:3 -> naa.6782bcb04cd61a00ff00005004f68696:3

141 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:5 -> naa.6782bcb04cd61a00ff00005004f68696:5

143 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:6 -> naa.6782bcb04cd61a00ff00005004f68696:6

145 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:7 -> naa.6782bcb04cd61a00ff00005004f68696:7

147 0 lrwxrwxrwx 1 root root 38 Jan 7 18:47 vml.02000000006782bcb04cd61a00ff00005004f68696504552432048:8 -> naa.6782bcb04cd61a00ff00005004f68696:8

istvankope · ‎01-08-2018

When I run the vmkfstools -V command I seen in the vmkernel.log the following:

2018-01-08T21:26:36.806Z cpu1:65660)FSS: 5764: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

2018-01-08T21:26:36.807Z cpu2:116284)VC: 4511: Device rescan time 49 msec (total number of devices 6)

2018-01-08T21:26:36.807Z cpu2:116284)VC: 4514: Filesystem probe time 259 msec (devices probed 4 of 6)

2018-01-08T21:26:36.807Z cpu2:116284)VC: 4516: Refresh open volume time 0 msec

2018-01-08T21:27:35.896Z cpu0:66025)NMP: nmp_ResetDeviceLogThrottling:3342: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x2 0x3a 0x2 from dev "mpx.vmhba1:C0:T0:L0" occurred 4 times(of 4 commands)

Is this normal?

Istvan

istvankope · ‎01-08-2018

And when I run vmkfstools --growfs /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696:3 /vmfs/devices/disks/naa.6782bcb04cd61a00ff00005004f68696:3

This is what I have in vmkernel.log:

2018-01-08T21:33:30.541Z cpu1:116344)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-08T21:33:30.541Z cpu1:116344)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-08T21:33:30.541Z cpu1:116344)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-08T21:33:30.544Z cpu1:116344)LVM: 4299: Device naa.6782bcb04cd61a00ff00005004f68696:3 is detected as being in volume 5708c03e-73a1841c-81a3-782bcb371d5b (0x4392f3c1b018)

2018-01-08T21:33:30.584Z cpu3:116344)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-08T21:33:30.584Z cpu3:116344)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-08T21:33:30.584Z cpu3:116344)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-08T21:33:30.584Z cpu3:116344)Vol3: 1006: Unable to register file system datastore1 for APD timeout notifications: Already exists

2018-01-08T21:33:30.584Z cpu3:116344)LVM: 10568: Error adding space (0) on device naa.6782bcb04cd61a00ff00005004f68696:3 to volume 5708c03e-73a1841c-81a3-782bcb371d5b: Not found

a_p_ · ‎01-09-2018

So you do have access to the datastore, but cannot expand it because it is detected as a snapshot!? That's strange.

What do you get when you run: esxcli storage vmfs snapshot list

André

istvankope · ‎01-09-2018

When I run esxcli storage vmfs snapshot list I get nothing, no result.

Istvan

a_p_ · ‎01-09-2018

Which exact ESXi version and build do you use? Maybe it is/was a known issue!?

Not sure whether it helps, but please post the output (if any) of the following commands too:

esxcli storage vmfs extent list

esxcli storage core device detached list

André

istvankope · ‎01-09-2018

ESXi version: 6.5.0 Update 1 (Build 6765664) / (Updated) DellEMC-ESXi-6.5U1-6765664-A04 (Dell)

esxcli storage vmfs extent list

Nothing

esxcli storage vmfs extent list

Volume Name VMFS UUID Extent Number Device Name Partition

----------- ----------------------------------- ------------- ------------------------------------ ---------

datastore1 5708c049-920c1595-7937-782bcb371d5b 0 naa.6782bcb04cd61a00ff00005004f68696 3

istvankope · ‎01-10-2018

Hello,

I upgraded to the latest version of ESXi: DellEMC-ESXi-6.5U1-7388607-A07 (Dell) , but this didn't solve the problem

I read somewhere that I should run the vmkfstools --growfs command with the full path to the partition like: mpx.vmhba33:C0:T0:L0:3 , but I don't know if this is valid in my case and I don't know how to find out this "full path".

Here is the end of vmkernel.log after the upgrade when I run the growfs command :

2018-01-10T15:27:47.558Z cpu1:65567)ScsiDeviceIO: 2948: Cmd(0x439500b28a80) 0x1a, CmdSN 0x857 from world 0 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:27:48.793Z cpu1:66022)NMP: nmp_ResetDeviceLogThrottling:3342: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x24 0x0 from dev "mpx.vmhba33:C0:T0:L1" occurred 1 times(of 1 commands)

2018-01-10T15:28:19.102Z cpu3:65560)ScsiDeviceIO: 2948: Cmd(0x439500be4200) 0x1a, CmdSN 0x867 from world 0 to dev "mpx.vmhba33:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:28:33.779Z cpu0:68665)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:28:33.779Z cpu0:68665)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:28:33.779Z cpu0:68665)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:28:33.780Z cpu0:68665)LVM: 4299: Device naa.6782bcb04cd61a00ff00005004f68696:3 is detected as being in volume 5708c03e-73a1841c-81a3-782bcb371d5b (0x439121c9b018)

2018-01-10T15:28:33.869Z cpu3:68665)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:28:33.869Z cpu3:68665)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:28:33.869Z cpu3:68665)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:28:33.869Z cpu3:68665)Vol3: 1006: Unable to register file system datastore1 for APD timeout notifications: Already exists

2018-01-10T15:28:33.869Z cpu3:68665)LVM: 10568: Error adding space (0) on device naa.6782bcb04cd61a00ff00005004f68696:3 to volume 5708c03e-73a1841c-81a3-782bcb371d5b: Not found

2018-01-10T15:28:43.234Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500afd200, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:43.234Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:43.234Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500afd200) 0x9e, CmdSN 0x889 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2018-01-10T15:28:43.261Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.743Z cpu1:68677)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:28:44.743Z cpu1:68677)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:28:44.743Z cpu1:68677)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:28:44.774Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500beed80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.774Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:44.774Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500beed80) 0x9e, CmdSN 0x8b0 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.784Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.789Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.789Z cpu1:65558)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x8b8 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.798Z cpu1:65558)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:44.800Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.809Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.809Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x8c6 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.822Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.831Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.831Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x8db from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.842Z cpu2:67969)ScsiDeviceIO: 2948: Cmd(0x439500af4d00) 0x1a, CmdSN 0x8e2 from world 0 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:28:44.845Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.853Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.853Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x8f0 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.868Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.876Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.876Z cpu1:65558)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x910 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.892Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.894Z cpu2:65559)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.894Z cpu2:65559)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x926 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.905Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.912Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.912Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x92f from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.925Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.927Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.927Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x932 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.943Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.945Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bc4680, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.945Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500bc4680) 0x9e, CmdSN 0x935 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.955Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.962Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b21000, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.962Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500b21000) 0x9e, CmdSN 0x939 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.976Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:44.985Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b21000, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:44.985Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500b21000) 0x9e, CmdSN 0x93f from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:44.995Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:45.003Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b21000, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:45.003Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500b21000) 0x9e, CmdSN 0x945 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:45.018Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:45.026Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b21000, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:45.026Z cpu3:65560)ScsiDeviceIO: 2962: Cmd(0x439500b21000) 0x9e, CmdSN 0x94b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:28:45.042Z cpu3:65560)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:28:45.050Z cpu0:65660)FSS: 5764: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

2018-01-10T15:28:46.668Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x28 (0x439500beed80, 0) to dev "mpx.vmhba33:C0:T0:L0" on path "vmhba33:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:46.668Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:46.668Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500beed80) 0x28, CmdSN 0x1 from world 0 to dev "mpx.vmhba33:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x22 0x20 0x46.

2018-01-10T15:28:47.352Z cpu1:65558)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:49.000Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba33:C0:T0:L0 repeated 2 times

2018-01-10T15:28:50.246Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x28 (0x439500b96b00, 0) to dev "mpx.vmhba33:C0:T0:L0" on path "vmhba33:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:28:50.246Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:50.246Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b96b00) 0x28, CmdSN 0x1 from world 0 to dev "mpx.vmhba33:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2018-01-10T15:28:50.932Z cpu2:65559)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:28:52.480Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba33:C0:T0:L0 repeated 2 times

2018-01-10T15:28:54.422Z cpu0:65669)FSS: 5764: No FS driver claimed device 'mpx.vmhba33:C0:T0:L0': No filesystem on the device

2018-01-10T15:28:54.439Z cpu2:68677)VC: 4511: Device rescan time 1555 msec (total number of devices 7)

2018-01-10T15:28:54.439Z cpu2:68677)VC: 4514: Filesystem probe time 9633 msec (devices probed 5 of 7)

2018-01-10T15:28:54.439Z cpu2:68677)VC: 4516: Refresh open volume time 17 msec

2018-01-10T15:28:58.665Z cpu0:68698)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:28:58.665Z cpu0:68698)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:28:58.665Z cpu0:68698)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:28:58.668Z cpu1:68698)LVM: 4299: Device naa.6782bcb04cd61a00ff00005004f68696:3 is detected as being in volume 5708c03e-73a1841c-81a3-782bcb371d5b (0x439122d1b018)

2018-01-10T15:28:58.701Z cpu1:68698)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:28:58.701Z cpu1:68698)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:28:58.701Z cpu1:68698)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:28:58.701Z cpu1:68698)Vol3: 1006: Unable to register file system datastore1 for APD timeout notifications: Already exists

2018-01-10T15:28:58.701Z cpu1:68698)LVM: 10568: Error adding space (0) on device naa.6782bcb04cd61a00ff00005004f68696:3 to volume 5708c03e-73a1841c-81a3-782bcb371d5b: Not found

2018-01-10T15:29:01.150Z cpu1:67552)ScsiDeviceIO: 2948: Cmd(0x439500bd2300) 0x1a, CmdSN 0x2 from world 67552 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:29:18.794Z cpu2:66022)NMP: nmp_ResetDeviceLogThrottling:3342: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x2 0x3a 0x2 from dev "mpx.vmhba1:C0:T0:L0" occurred 4 times(of 4 commands)

2018-01-10T15:30:00.094Z cpu3:65821)ScsiDeviceIO: 2948: Cmd(0x439500b30180) 0x1a, CmdSN 0x9e8 from world 0 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:30:06.902Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b24480, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:06.902Z cpu1:65558)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:06.902Z cpu1:65558)ScsiDeviceIO: 2962: Cmd(0x439500b24480) 0x9e, CmdSN 0x9f1 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2018-01-10T15:30:06.913Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:07.973Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500bee300, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:07.973Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba1:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:07.973Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500bee300) 0x9e, CmdSN 0x9fd from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:07.986Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.005Z cpu1:67805 opID=595d494)World: 12235: VC opID aa5864d3 maps to vmkernel opID 595d494

2018-01-10T15:30:08.005Z cpu1:67805 opID=595d494)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:30:08.006Z cpu1:67805 opID=595d494)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:30:08.006Z cpu1:67805 opID=595d494)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:30:08.007Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.007Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa1d from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.013Z cpu2:65675)ScsiDeviceIO: 2948: Cmd(0x439500b13000) 0x1a, CmdSN 0xa5e from world 0 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:30:08.017Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.026Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.026Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa7b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.038Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.046Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.046Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa81 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.060Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.068Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.068Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa87 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.084Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.092Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.092Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa8d from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.108Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.110Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b3cc80, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.110Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b3cc80) 0x9e, CmdSN 0xa91 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.123Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.130Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b99880, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.130Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b99880) 0x9e, CmdSN 0xa95 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.143Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.145Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b99880, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.145Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b99880) 0x9e, CmdSN 0xa98 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.159Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.161Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500b99880, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.161Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b99880) 0x9e, CmdSN 0xa9b from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.174Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.181Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500ba8a00, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.181Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500ba8a00) 0x9e, CmdSN 0xa9f from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.194Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.203Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500ba8a00, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.203Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500ba8a00) 0x9e, CmdSN 0xaa5 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.216Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.225Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500ba8a00, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.225Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500ba8a00) 0x9e, CmdSN 0xaab from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.238Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.247Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x9e (0x439500ba8a00, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:08.247Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500ba8a00) 0x9e, CmdSN 0xab1 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x46 0x61 0x69.

2018-01-10T15:30:08.260Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2018-01-10T15:30:08.269Z cpu0:65662)FSS: 5764: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

2018-01-10T15:30:09.957Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x28 (0x439500b9d780, 0) to dev "mpx.vmhba33:C0:T0:L0" on path "vmhba33:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:09.957Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:09.957Z cpu0:65557)ScsiDeviceIO: 2962: Cmd(0x439500b9d780) 0x28, CmdSN 0x1 from world 0 to dev "mpx.vmhba33:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2018-01-10T15:30:11.311Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:12.293Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba33:C0:T0:L0 repeated 2 times

2018-01-10T15:30:13.848Z cpu1:65558)NMP: nmp_ThrottleLogForDevice:3647: Cmd 0x28 (0x439500b9d780, 0) to dev "mpx.vmhba33:C0:T0:L0" on path "vmhba33:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2018-01-10T15:30:13.848Z cpu1:65558)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:13.848Z cpu1:65558)ScsiDeviceIO: 2962: Cmd(0x439500b9d780) 0x28, CmdSN 0x1 from world 0 to dev "mpx.vmhba33:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2018-01-10T15:30:15.199Z cpu0:65557)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba33:C0:T0:L0" state in doubt; requested fast path state update...

2018-01-10T15:30:16.175Z cpu0:65557)NMP: nmp_ThrottleLogForDevice:3593: last error status from device mpx.vmhba33:C0:T0:L0 repeated 2 times

2018-01-10T15:30:18.361Z cpu0:65671)FSS: 5764: No FS driver claimed device 'mpx.vmhba33:C0:T0:L0': No filesystem on the device

2018-01-10T15:30:18.373Z cpu1:67805 opID=595d494)VC: 4511: Device rescan time 1106 msec (total number of devices 7)

2018-01-10T15:30:18.373Z cpu1:67805 opID=595d494)VC: 4514: Filesystem probe time 10354 msec (devices probed 5 of 7)

2018-01-10T15:30:18.373Z cpu1:67805 opID=595d494)VC: 4516: Refresh open volume time 12 msec

2018-01-10T15:30:48.795Z cpu2:66022)NMP: nmp_ResetDeviceLogThrottling:3342: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x2 0x3a 0x2 from dev "mpx.vmhba1:C0:T0:L0" occurred 4 times(of 4 commands)

2018-01-10T15:30:56.621Z cpu3:67648)ScsiDeviceIO: 2948: Cmd(0x439500acbe80) 0x1a, CmdSN 0xb1f from world 0 to dev "naa.6782bcb04cd61a00ff00005004f68696" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-01-10T15:33:11.799Z cpu1:68780)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:33:11.799Z cpu1:68780)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:33:11.799Z cpu1:68780)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:33:11.800Z cpu0:68780)LVM: 4299: Device naa.6782bcb04cd61a00ff00005004f68696:3 is detected as being in volume 5708c03e-73a1841c-81a3-782bcb371d5b (0x43912561b018)

2018-01-10T15:33:11.832Z cpu0:68780)LVM: 11138: Device naa.6782bcb04cd61a00ff00005004f68696:3 detected to be a snapshot:

2018-01-10T15:33:11.832Z cpu0:68780)LVM: 11145: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 6882185633125510635>

2018-01-10T15:33:11.832Z cpu0:68780)LVM: 11152: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5662250421448700996>

2018-01-10T15:33:11.832Z cpu2:68780)Vol3: 1006: Unable to register file system datastore1 for APD timeout notifications: Already exists

2018-01-10T15:33:11.832Z cpu2:68780)LVM: 10568: Error adding space (0) on device naa.6782bcb04cd61a00ff00005004f68696:3 to volume 5708c03e-73a1841c-81a3-782bcb371d5b: Not found

All

datastore resize problems