Applies to ONTAP 9 FabricPool-enabled aggregates Aggregate space Issue Large VMDK file Not enough space in the FabricPool-enabled aggregate than the VMDK file size VCenter is migrating the VDMK file b...Applies to ONTAP 9 FabricPool-enabled aggregates Aggregate space Issue Large VMDK file Not enough space in the FabricPool-enabled aggregate than the VMDK file size VCenter is migrating the VDMK file because there is not enough space available Tiering policy is set to all
Assuming that the aggregate usage increased to nearly 100% after the upgrade, and that ONTAP forced the WAFL reserve percentage back to 10% due to the revert, this may result in aggregate space issues...Assuming that the aggregate usage increased to nearly 100% after the upgrade, and that ONTAP forced the WAFL reserve percentage back to 10% due to the revert, this may result in aggregate space issues For FAS platforms, the WAFL reserve for aggregates greater than 30TB in size is reduced from 10% to 5%, resulting in increased usable space in the aggregate
Applies to AFF systems Comparing to HDD aggregated where we might see performance issue in highly utilized environment with SSD aggregates this shouldn't be a case. This is due to differences in techn...Applies to AFF systems Comparing to HDD aggregated where we might see performance issue in highly utilized environment with SSD aggregates this shouldn't be a case. This is due to differences in technology used to access the data. HDD disks have mechanical parts and different design which has big contribution in system performance SSD disks use a different technology and don't have mechanical parts. Therefore the access to the data is faster and shouldn't be affect by how full is the aggregate
