Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • 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/OHW/OHW-KBs/How_to_limit_NFS_access_to_the_SVM_root_volume
      By default, when an SVM is created, the root volume is configured with 755 permissions. When this is configured, everyone who accesses the SVM root volume can list and read junctions mounted below the...By default, when an SVM is created, the root volume is configured with 755 permissions. When this is configured, everyone who accesses the SVM root volume can list and read junctions mounted below the SVM root volume. In addition, the default export policy rule that is created when an SVM is configured using System Manager or vserver setup commands permits user access to the SVM root. All would be mounted under "/" and can be listed with the ls command by any user accessing the mount.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_could_cause_an_SVM_root_volume_to_go_full
      Applies to ONTAP 9 Answer Can be caused by a previously renamed volume still being present in the svm root (with the original name) in which data is still being written to. This volume is not junction...Applies to ONTAP 9 Answer Can be caused by a previously renamed volume still being present in the svm root (with the original name) in which data is still being written to. This volume is not junctioned/mounted into the svm root, but access via NAS protocols could still be possible. Additional Information Please contact NetApp Technical Support and reference this article to confirm if this is the case.