Cold data can't be moved to capacity tier even tiering scanner looks like running
Applies to
- ONTAP 9
- FabricPool
- Impacted tiering policies: 'Auto', 'Snapshot-Only', 'All'
Issue
- By default, tiering scanner runs every 24 hours.
- Tiering scanner runs and completes every day but it does not tier all the cold data.
- Once reboot the node, tiering scanner runs again and data movement happens, but the symptom will be probably encountered the next day.
- For the normal (without node reboot) scanner runs for seconds whereas after reboot the scanner takes hours to complete and data movement happening.
Example:
EMS log to show the normal (without node reboot) scanner runs for seconds and then abort.
Feb 12 13:19:59 JST [node name: scan_ca_tiering_wkr: wafl.scan.start:debug]: Starting composite aggregate tiering on volume volume-name@vserver:xxxx.
Feb 12 13:20:57 JST [node name: wafl_scan_exempt: wafl.scan.done:notice]: Completed composite aggregate tiering on volume volume-name@vserver:xxxx.
EMS log to show after reboot the scanner takes hours to complete.
Feb 10 12:52:05 JST [node name: scan_ca_tiering_wkr: wafl.scan.start:debug]: Starting composite aggregate tiering on volume volume-name@vserver:xxxx.
Feb 10 14:03:29 JST [node name: wafl_scan_exempt: wafl.scan.done:notice]: Completed composite aggregate tiering on volume volume-name@vserver:xxxx.