Search

Why ILM placement unachievable alert didn't come up at the time of StorageGRID upgrade when it wasn't able to fulfil the minimum nodes required for EC?
https://kb.netapp.com/hybrid/StorageGRID/Maintenance/Why_ILM_placement_unachievable_alert_didn_t_come_up_at_the_time_of_StorageGRID_upgrade_when_it_wasn_t_able_to_fulfil_the_minimum_nodes_required_for_EC
During the upgrade, the ingest object size could be less than 1 MB, resulting in the ILM rule for using the EC profile not being applied. Alerts are generated when ingestions occur, and the ILM rule i...During the upgrade, the ingest object size could be less than 1 MB, resulting in the ILM rule for using the EC profile not being applied. Alerts are generated when ingestions occur, and the ILM rule is not fulfilled, however, the ILM rule for the EC profile was not checked due to the smaller object size. Consequently, no alerts were generated for the site during the upgrade. The Audit-Explain tool can be used to check the object size in bytes during the upgrade timeframe.
SVMDR reverse resync or resync fail with error No space left on device
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVMDR_reverse_resync_or_resync_fail_with_error_No_space_left_on_device
SVMDR failover testing fails during resync with errors stating "No space left on device" status=Failure message=Failed to start transfer for Snapshot copy "vserverdr.2.c656c098-a77a-11e9-b9f7-00a098fd...SVMDR failover testing fails during resync with errors stating "No space left on device" status=Failure message=Failed to start transfer for Snapshot copy "vserverdr.2.c656c098-a77a-11e9-b9f7-00a098fd4512.2025-05-24_235020".(Failed to start transfer.(Filesystem error(No space left on device)))