Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 24 results
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Linux_host_reporting_different_space_utilization_than_ONTAP
      Applies to ONTAP 9 Linux Space Utilization Issue Linux host reporting different space utilization than ONTAP.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Fractional_reserve_is_being_allocated_even_though_no_snapshots_exist
      Applies to ONTAP 9 Clustered Data ONTAP 8 ONTAP 8.x 7-Mode FlexPod Issue A volume containing a thin LUN with Fractional Reserve is 100% No snapshots exist on the volume The space reported in the volum...Applies to ONTAP 9 Clustered Data ONTAP 8 ONTAP 8.x 7-Mode FlexPod Issue A volume containing a thin LUN with Fractional Reserve is 100% No snapshots exist on the volume The space reported in the volume is greater than the space reported in the LUN After enabling Space-Allocation LUN not reflecting free space after deletion
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_is_there_a_difference_in_space_usage_in_quota_report_and_a_UNIX_client
      The difference in usage values is because of the difference in methods followed by the quota report and the UNIX commands for calculating the data blocks in the volume or qtree. However, when the volu...The difference in usage values is because of the difference in methods followed by the quota report and the UNIX commands for calculating the data blocks in the volume or qtree. However, when the volume is mounted on a UNIX client and the file is shown as the output of the ls command, the empty data blocks are also included in the space usage.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_is_there_no_difference_for_field_logical_available_in_vol_show_and_vol_show_space_when_logical_space_reporting_is_enabled
      By default, we only populate logical-available when logical reporting is enabled on the volume: ::> vol show -volume vol1 -fields logical-available fas8200-2n-ams-1::> vol show -volume vol1 -fields lo...By default, we only populate logical-available when logical reporting is enabled on the volume: ::> vol show -volume vol1 -fields logical-available fas8200-2n-ams-1::> vol show -volume vol1 -fields logical-available The vol show-space command will give back logical-available regardless if logical space reporting is enabled: ::> vol show-space -volume vol1 -fields logical-available Showing logical-available through vol show-space command is not intended and will be fixed in future releases.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_is_the_used_percentage_different_in_Linux_from_the_one_in_NetApp
      In Netapp, the volume size is: Available size + Netapp used size + over provisioned size. In Linux, the volume size is: Available size + Linux used size. Linux used size = Netapp used size + over prov...In Netapp, the volume size is: Available size + Netapp used size + over provisioned size. In Linux, the volume size is: Available size + Linux used size. Linux used size = Netapp used size + over provisioned size. Vserver Volume Aggregate State Type Size Available Used% The Netapp used size percentage is therefore 331/480= 69%. Linux used size = Netapp used size + over provisioned size = 331TB + 84TB = 415TB. The Linux used size percentage is therefore 415/480 =86%:
    • https://kb.netapp.com/data-mgmt/OCI_Kbs/Space_accounting_discrepancy_between_ONTAP_OnCommand_Insight
      Applies to ONTAP 9 OnCommand Insight Space Accounting Issue Space accounting discrepancy between ONTAP and OnCommand Insight 20.9TB used capacity reported in OnCommand Insight: 18.02TB used capacity r...Applies to ONTAP 9 OnCommand Insight Space Accounting Issue Space accounting discrepancy between ONTAP and OnCommand Insight 20.9TB used capacity reported in OnCommand Insight: 18.02TB used capacity reported by ONTAP via volume show: Volume Aggregate State Type Size (TB) Available (TB) Used Used% fg__0006 Aggr1 online RW 25.00 6.98 18.02TB 72
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_Source_and_Destination_shows_different_Aggregate_Footprint
      Applies to Ontap 9.x SnapMirror Issue Source and Destination Aggregate have a difference in the Volume Footprint even when all volumes are the same Cluster::> aggr show-space Aggregate : aggr0 Feature...Applies to Ontap 9.x SnapMirror Issue Source and Destination Aggregate have a difference in the Volume Footprint even when all volumes are the same Cluster::> aggr show-space Aggregate : aggr0 Feature Used Used% -------------------------------- ---------- ------ Volume Footprints 5.19GB 49% Aggregate Metadata 588KB 0% Snapshot Reserve 540MB 5% Total Used 5.71GB 54% Total Physical Used 4.54GB 43%
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Snapmirror_Destination_volume_space_usage_in_aggregate_is_different_to_Source_volume
      Applies to SnapMirror ONTAP 9.x Issue Destination volume takes much more or much less space in the aggregate than on the source cluster/aggregate
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Newly_created_snapshots_by_user_will_get_deleted_immediately_or_shortly_after
      Applies to ONTAP 9 Issue Manually created snapshots will get deleted straight or shortly after the snapshot create command or API is issued.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_verify_what_is_eating_up_space_in_an_SVM_root_volume
      Applies to ONTAP 9 Data ONTAP 8 Description How to check what is consuming space in an SVM root volume.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_is_the_volume_reporting_nearly_full_when_half_of_the_volume_is_being_tiered_to_the_capacity_tier
      Applies to ONTAP 9 Answer The command volume show reports what is on both the performance and capacity tiers You can see how the storage is distributed between the performance tier and the capacity ti...Applies to ONTAP 9 Answer The command volume show reports what is on both the performance and capacity tiers You can see how the storage is distributed between the performance tier and the capacity tier using vol status -f on the node shell Additional Information