Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/tsse_scan_start_failed__Cold_Data_Scan_failed_to_start
      Applies to Storage Efficiency/ Data Compression Temperature Sensitive Storage Efficiency (TSSE) Every time when the data compression runs, it gives out the following error: vol efficiency inactive-dat...Applies to Storage Efficiency/ Data Compression Temperature Sensitive Storage Efficiency (TSSE) Every time when the data compression runs, it gives out the following error: vol efficiency inactive-data-compression show -vserver vs0 -volume vol1 Volume: vol1 Vserver: vs0 Is Enabled: true Status: FAILURE Failure Reason: Scan was stopped event log show ERROR tsse.scan.start.failed: 'Cold Data Scan' failed to start on 'vol1' - Scan was stopped The issue started after enabling the FabricPool.
    • https://kb.netapp.com/on-prem/ontap/DM/Efficiency/Efficiency-KBs/No_compression_reporting_0_savings_in_ONTAP_9_8_or_later_at_the_volume_level_and_aggregate_level
      Temperature-sensitive storage efficiency was introduced in ONTAP 9.8 and was enabled automatically on newly created thin-provisioned AFF volumes. Compression is not achieved at the volume level anymo...Temperature-sensitive storage efficiency was introduced in ONTAP 9.8 and was enabled automatically on newly created thin-provisioned AFF volumes. Compression is not achieved at the volume level anymore, earlier compression savings were displayed through the df command's -S option which is deprecated going forward and will always show 0 for compression. On TSSE-enabled volumes, all compression savings are reflected at the aggregate layer.
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/High_read_latency_seen_after_controller_upgrade_from_AFF-A400_to_other_platforms
      Applies to ONTAP 9 Non AFF-A400 Issue High read latency is seen due to decompression after upgrading from an AFF A400 system. after SnapMirror data transfering from an AFF A400 system. ActiveIQ report...Applies to ONTAP 9 Non AFF-A400 Issue High read latency is seen due to decompression after upgrading from an AFF A400 system. after SnapMirror data transfering from an AFF A400 system. ActiveIQ reports the below risk: Volumes migrated off an AFF-A400 that use the lzrw1a compressiong algorithm to a different model may experience higher latency.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Volume_efficiency_start_failing_with_error_Compression_is_not_enabled._Use_of_options_-a_and_-b_is_not_valid
      Warning: This operation scans all of the data in volume "vol1" of Vserver "svm1". It might take a significant time, and degrade performance during that time. Use of "-snapshot-blocks|-b" option can in...Warning: This operation scans all of the data in volume "vol1" of Vserver "svm1". It might take a significant time, and degrade performance during that time. Use of "-snapshot-blocks|-b" option can increase space usage as data which is part of Snapshot will be compressed. Error: command failed: Failed to start efficiency on volume "vol1" of Vserver "svm1": Compression is not enabled. Use of options -a and -b is not valid.