Skip to main content
NetApp Knowledge Base

Does SnapMirror (XDP) change inode IDs?

  1. Last updated
  2. Save as PDF
Views:
7
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • NetApp ONTAP
  • SnapMirror (XDP)

Answer

  • SnapMirror (XDP) preserves inode IDs during replication.
  • The inode IDs of files within the volume remain unchanged between source and destination volumes.

Additional Information

  • After a SnapMirror break:
    • The destination volume becomes read-write and is assigned a new volume UUID (FSID).
    • This causes the device identifier (st_dev) to change from the NFS client perspective.
  • File identification on NFS: 
    • A combination of identity files:
      • inode number (st_ino)
      • device number (st_dev) 
    • Even if the inode number remains unchanged, a change in st_dev causes the file to be recognized as a different file.
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.