Five minutes ago, you performed a single file SnapRestore on a large NFS file. 40% of your NFS users are now complaining about getting "stale file handles" for the file. Which is the most likely…

Question

Options

• AThis might be due to an NFS storage system and client mismatch.
• BNFS users why try to access a reverted file without first reopening it might get a "stale file handle" error
• CAfter a single file SnapRestore, NFS users have to reboot their systems. Have them reboot their systems.
• DThese users are on a different subnet from the others. Start troubleshooting by checking their subnet.

• A
  4% (1)
• B
  79% (22)
• C
  4% (1)
• D
  14% (4)

Explanation

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-35C9A4BA-02BA-4965-A366- 698C1299E29D.html Reverting a file to a selected Snapshot copy Using snap restore to revert a single file to a selected Snapshot copy is practical when the file is so large that you cannot copy the previous file version from the Snapshot copy to the active file Before you begin Ensure that you notify the network users before reverting a file so that they know that the current data in the file will be replaced by that of the selected Snapshot copy. Note: NFS users who try to access a reverted file without first reopening it might get a stale file handle error message after the volume reversion.

No community discussion yet for this question.