Why does modifying the volume option "-snapdir-access" require a re-mount?
Applies to
- ONTAP 9
- NFSv3
Answer
- The behavior depends on whether the client sends a V3 LOOKUP call.
- If the client sends a V3 LOOKUP call, the storage system will respond appropriately based on the current -snapdir-access setting.
- If the client refers to the local directory caches and does not send a V3 LOOKUP call, the new -snapdir-access setting on the storage side will not take effect.
Example:
-snapdir-access disabled:
80 2024-04-06 14:25:00.017290 0.000079 Client_IP 698 Storage_IP 2049 NFS 226 V3 LOOKUP Call (Reply In 81), DH: 0x69edfd3b/.snapshot81 2024-04-06 14:25:00.017384 0.000094 Storage_IP 2049 Client_IP 698 NFS 186 V3 LOOKUP Reply (Call In 80) Error: NFS3ERR_NOENT[root@centos1 mnt]# cd .snapshot-bash: cd: .snapshot: No such file or directory-snapdir-access enabled:
82 2024-04-06 14:52:03.471510 0.000067 Client_IP 978 Storage_IP 2049 NFS 226 V3 LOOKUP Call (Reply In 83), DH: 0x69edfd3b/.snapshot83 2024-04-06 14:52:03.471599 0.000089 Storage_IP 2049 Client_IP 978 NFS 322 V3 LOOKUP Reply (Call In 82), FH: 0x0408dcdd[root@centos1 mnt]# cd .snapshot[root@centos1 .snapshot]#Additional Information
additionalInformation_text
