Skip to content

Commit 18bea7e

Browse files
Merge pull request #217628 from b-ahibbard/anf-nfs-snapshotpath
hide snapshot path updates
2 parents d58ba09 + 3282499 commit 18bea7e

File tree

3 files changed

+12
-3
lines changed

3 files changed

+12
-3
lines changed

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 10/25/2022
15+
ms.date: 11/08/2022
1616
ms.author: anfdocs
1717
---
1818
# Create an NFS volume for Azure NetApp Files
@@ -98,6 +98,9 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
9898

9999
![Show advanced selection](../media/azure-netapp-files/volume-create-advanced-selection.png)
100100

101+
>[!NOTE]
102+
>By default, the `.snapshot` directory path is hidden from NFSv4.1 clients. Enabling the **Hide snapshot path** option will hide the .snapshot directory from NFSv3 clients; the directory will still be accessible.
103+
101104
3. Click **Protocol**, and then complete the following actions:
102105
* Select **NFS** as the protocol type for the volume.
103106

articles/azure-netapp-files/convert-nfsv3-nfsv41.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: how-to
15-
ms.date: 06/06/2022
15+
ms.date: 11/08/2022
1616
ms.author: anfdocs
1717
---
1818
# Convert an NFS volume between NFSv3 and NFSv4.1
@@ -39,6 +39,8 @@ Converting a volume between NFSv3 and NFSv4.1 does not require that you create a
3939
* You cannot convert a single-protocol NFS volume to a dual-protocol volume, or the other way around.
4040
* You cannot convert a destination volume in a cross-region replication relationship.
4141
* Converting an NFSv4.1 volume to NFSv3 will cause all advanced NFSv4.1 features such as ACLs and file locking to become unavailable.
42+
* Converting a volume from NFSv3 to NFSv4.1 will cause the `.snapshot` directory to be hidden from NFSv4.1 clients. The directory will still be accessible.
43+
* Converting a volume from NFSv4.1 to NFSv3 will cause the `.snapshot` directory to be visible. You can modify the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
4244

4345
## Register the option
4446

articles/azure-netapp-files/faq-nfs.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.workload: storage
66
ms.topic: conceptual
77
author: b-hchen
88
ms.author: anfdocs
9-
ms.date: 08/03/2022
9+
ms.date: 11/08/2022
1010
---
1111
# NFS FAQs for Azure NetApp Files
1212

@@ -50,6 +50,10 @@ For example, if a client mounting a volume becomes unresponsive or crashes beyon
5050

5151
A grace period defines a period of special processing in which clients can try to reclaim their locking state during a server recovery. The default timeout for the leases is 30 seconds with a grace period of 45 seconds. After that time, the client's lease will be released.
5252

53+
## Why is the `.snapshot` directory not visible in an NFSv4.1 volume, but it is visible in an NFSv3 volume?
54+
55+
By design, the .snapshot directory is never visible to NFSv4.1 clients. By default, the `.snapshot `directory will be visible to NFSv3 clients. To hide the `.snapshot` directory from NFSv3 clients, edit the properties of the volume to [hide the snapshot path](snapshots-edit-hide-path.md).
56+
5357
## Oracle dNFS
5458

5559
### Are there any Oracle patches required with dNFS?

0 commit comments

Comments
 (0)