Applies to MetroCluster Answer Yes, NetApp Flash Pool caching is supported in MetroCluster configurations. Each Flash Pool aggregate must contain an identical plex on each site (if it is a mirrored ag...Applies to MetroCluster Answer Yes, NetApp Flash Pool caching is supported in MetroCluster configurations. Each Flash Pool aggregate must contain an identical plex on each site (if it is a mirrored aggregate). Additional Information additionalInformation_text
Flash Pool / Storage Pool Aggregate (Hybrid aggregate) After upgrading ONTAP to 9.7P14, the system triggers a warning once per week: Aggregate data_aggr (online, mixed_raid_type, hybrid) (block checks...Flash Pool / Storage Pool Aggregate (Hybrid aggregate) After upgrading ONTAP to 9.7P14, the system triggers a warning once per week: Aggregate data_aggr (online, mixed_raid_type, hybrid) (block checksums) RAID group /data_aggr/plex0/rg1 (normal, block checksums, raid4) RAID group /data_aggr/plex0/rg2 (normal, block checksums, raid4) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) No spare drives available for the RAID groups with SSDs
No, a RAID Group (such as a Flash Pool allocation) cannot be removed from an aggregate without destroying the aggregate, first. In order to remove Flash Pool from an existing aggregate, you would firs...No, a RAID Group (such as a Flash Pool allocation) cannot be removed from an aggregate without destroying the aggregate, first. In order to remove Flash Pool from an existing aggregate, you would first need to migrate the volumes (data) to a different aggregate before destroying the existing Flash Pool aggregate. The SSDs will then be returned to the spares pool for the system. It is possible to disable caching of the Flash Pool for testing purposes.
Applies to ONTAP 9.x Flash Pool Issue In a rare situation, Flash Pool can have cached data that does not match with the original data. The following combinations of EMS logs are observed, no loss of d...Applies to ONTAP 9.x Flash Pool Issue In a rare situation, Flash Pool can have cached data that does not match with the original data. The following combinations of EMS logs are observed, no loss of data has happened because the correct data is still available and is delivered: raid.cksum.wc.blkErr:EMERGENCY raid.data.lw.blkErr:critical wafl.raid.incons.ssd.cached.buf:error callhome.micro.core:error callhome.checksum.multiple:alert
The following warning is displayed when moving a volume from a flash pool aggregate: ::> volume move start -vserver svm1 -volume vol1 -destination-aggregate aggr1 Warning: Cannot preserve the caching ...The following warning is displayed when moving a volume from a flash pool aggregate: ::> volume move start -vserver svm1 -volume vol1 -destination-aggregate aggr1 Warning: Cannot preserve the caching policy associated with volume "vol1" in the destination aggregate "aggr1". If you continue, caching policy will be disabled in the destination. The above warning can also be displayed while moving a volume from a FAS system with a flash pool to an aggregate on AFF system.
