We got a from 6.7 Upgraded Environment (vSphere and vCenter) with attached HPE 3PAR FC Storage.
The configured vSphere Cluster got multiple LUNs which are VMFS 5 and VMFS 6 Datastores and also RAW Devices.
If we now (after Upgrade to V 7) extend a LUN (800 to 900 GB) the VCenter don´t show any VMFS 6 Datastores (local VMFS 6 Datastores on a local SSD too), just the VMFS 5 Datastores you could see under Datastores.
On a VM-Host HBA you could still see all LUNs (including the VMFS 6 LUNs), but on the VMFS 6 LUNs in the column Datastore you could just see "not used".
New Size will be shown. This does not appear to all Hosts (alle same Hardware and Version) in the Cluster but on different Hosts on further LUN extensions.
VMs on a VMFS 6 Store will still work normal (read & write on the VMDKs) but will appear as OFFLINE in VCenter after a while.
Also HA will try to do a Failover / VMotion (which will fail for VMs that are on VMFS 6 Datastores) if a VMFS 6 store is used as Heartbeat-Datastore.
Sometimes a Restart of the Server Agent will solve this problem. And some times if you will end a VM (with VMDK on a VMFS6 LUN) on this hanging Host.
Rescan of HBAs and VMFS = don´t help
Restart of VCenter Node = don´t help
Disabling HA and DRS before extending the LUN = don´t help
Got anyone se same problems or a solution ?
Looks like following Problem
VMware Knowledge Base (KB80188)
will be fixed with vSphere 7 U1
First test:
check if the datastore is detected as a snapshot
Did you restart host (power off/on to reinitialize HBA firmware) ?
Can you please share vmkernel.log?
continuum
The VMFS 6 Stores are not detected as Snapshots.
DominikWeglarz
Could not restart the Host because there is still a VM running (without problems) which is stored on this VMFS 6 Datastore.
It will be shown as "xxxxx (inaccessible)" so i could not do a Vmotion.
We Reinstalled (overwrite not upgrade) all Vsphere Hosts directly with Version 7.0 (not Upgrade 6.5>6.7>7.0).
Additionally we got a MS Cluster Running on that Environment we now delete so that there are NOW only regular VMDKs and RAW Disks.
Now we could extend VMFS and RAW Disks without that the VMFS6 Stores will disappear on the Vsphere 7 Hosts.
So it looks like a Upgrade Problem (6.7 to 7 on HPE) or a Problem with the Disk Reservation if you got Microsoft Cluster on Vsphere.
For us it is now solved
Again after Extend a VMFS LUN RAW on VM) on our 3PAR Storage, the VMFS6 Volumes dissapeared on all vsphere 7 Hosts. On a few they come back after Restarting the Management Agents but again on 3 Servers it don´t work.
(VMs that will run on such a VMFS6 Datastore will shown as "inaccessible" in VCenter but still running fine, we just could not manage it over the VCenter but)
Looks like following Problem
VMware Knowledge Base (KB80188)
will be fixed with vSphere 7 U1