After a single file SnapRestore, some NFS users encounter stale file handles unless they do what?

After a single file SnapRestore, some NFS users encounter stale file handles unless they do what?

• A. Reopen the file
• B. Reboot the clients
• C. Recreate the file on server
• D. Restore the directory

Answer: (A)

After a single-file SnapRestore, the server’s view of that file can change, which can leave NFS clients with a cached, now-invalid file handle. Reopening the file on the client forces a new open operation, causing the client to fetch a fresh file handle from the server and update its cache. With the updated handle, access resumes normally. Rebooting the clients is more disruptive and unnecessary, recreating the file on the server would alter the file itself, and restoring the directory doesn’t address the stale handle for a single file.

After a single-file SnapRestore, the server’s view of that file can change, which can leave NFS clients with a cached, now-invalid file handle. Reopening the file on the client forces a new open operation, causing the client to fetch a fresh file handle from the server and update its cache. With the updated handle, access resumes normally. Rebooting the clients is more disruptive and unnecessary, recreating the file on the server would alter the file itself, and restoring the directory doesn’t address the stale handle for a single file.