Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Accessing_snapshot_mount_points_results_in_a_stale_file_handle
      Applies to ONTAP 9 Issue df -h command from the Linux client returns stale file handle for some snapshot mount points Example: [root@linuxl datal]# df -h df: '/path1/snapshot/file1: 572494d9-29/0-11ee...Applies to ONTAP 9 Issue df -h command from the Linux client returns stale file handle for some snapshot mount points Example: [root@linuxl datal]# df -h df: '/path1/snapshot/file1: 572494d9-29/0-11ee-9809-403025423ba2153234085: 2024-02-23 181500': State file handle df: '/path2/.snapshot/file2: 572494d9-29f0-11ee-9809-dO39ea5423ba_2153234085.2024-03-20_001500': Stae file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_error_NFSv3_and_NFSV4_due_to_flipping_SnapMirror_relationship_between_two_sites
      Applies to ONTAP 9 SnapMirror NFSv3 \ NFSv4 Issue UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: clien...Applies to ONTAP 9 SnapMirror NFSv3 \ NFSv4 Issue UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host filer: Stale file handle [file handle: 38c000 f6830500 20000000 4f6f41 52809302 6180000 38c000 f6830500]message: Stale file handle At the same time there was a flip of SnapMirror relationship between sites
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_caused_by_file_or_directory_in_use_or_deleted_by_another_client
      Applies to ONTAP 9 Issue Client or application is reporting a stale file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_error_NFSv3_and_NFSV4
      Applies to ONTAP 9 Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host...Applies to ONTAP 9 Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host filer: Stale file handle [file handle: 38c000 f6830500 20000000 4f6f41 52809302 6180000 38c000 f6830500]message: Stale file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_error_NFSv3_and_NFSV4_due_to_a_file_system_exported_by_the_storage_system_is_not_exported_to_a_client
      Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [...Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host filer: Stale file handle [file handle: 38c000 f6830500 20000000 4f6f41 52809302 6180000 38c000 f6830500]message: Stale file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/A_Linux_system_running_kernel_2.6x_creates_a_mount_point_when_accessing_the_.snapshot_directory_via_Network_File_System
      Modern Linux clients identifies the .snapshot directory as a different filesystem, and thus as a different mount point When the snapshot is deleted, clients report stale file handle for .snapshot base...Modern Linux clients identifies the .snapshot directory as a different filesystem, and thus as a different mount point When the snapshot is deleted, clients report stale file handle for .snapshot based sub-mounts Restart of the server resolve the issue but again the next day receiving the same stale file handle issue with the previous day's snapshot which is already deleted: mount command on the Linux host displays a large number of snapshots mounted and is not able to unmount
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_error_NFSv3_and_NFSV4_due_to_a_file_or_directory_in_use_is_deleted_by_another_client
      Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [...Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host filer: Stale file handle [file handle: 38c000 f6830500 20000000 4f6f41 52809302 6180000 38c000 f6830500]message: Stale file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Stale_file_handle_error_NFSv3_and_NFSV4_due_to_pNFS_device_ID_does_not_exist_and_the_I_O_request_comes_to_the_DS_Data_Serving
      Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [...Applies to ONTAP 9 Data ONTAP 8 7-Mode Issue A UNIX client reports stale file handle using either NFSv3 or NFSv4 A typical message in the client's syslog may look like the following: message: client [unix]: write on host filer: Stale file handle [file handle: 38c000 f6830500 20000000 4f6f41 52809302 6180000 38c000 f6830500]message: Stale file handle
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/After_upgrading_to_ONTAP_9_7_getting_fileid_changed_or_stale_file_handle_on_client
      Applies to ONTAP 9.7 - 9.7P6 NFS 4.x Issue After upgrading to ONTAP 9.7, NFS 4.x clients start seeing : NFS: server error: fileid changed expected fileid 0x4740f54, got 0x8000047400000f54 "stale file ...Applies to ONTAP 9.7 - 9.7P6 NFS 4.x Issue After upgrading to ONTAP 9.7, NFS 4.x clients start seeing : NFS: server error: fileid changed expected fileid 0x4740f54, got 0x8000047400000f54 "stale file handle"