Skip to content

Commit 8883175

Browse files
authored
Merge pull request #230615 from b-ahibbard/revert-breakfilelocks
Revert breakfilelocks
2 parents c701d29 + b2aa5d9 commit 8883175

File tree

5 files changed

+5
-40
lines changed

5 files changed

+5
-40
lines changed

articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,11 @@
3939
"source_path_from_root": "/articles/azure-vmware/restore-azure-netapp-files-vms.md",
4040
"redirect_url": "/azure/azure-vmware/",
4141
"redirect_document_id": false
42+
},
43+
{
44+
"source_path_from_root": "/articles/azure-netapp-files/troubleshoot-file-locks.md",
45+
"redirect_url": "/azure/azure-netapp-files/faq-nfs",
46+
"redirect_document_id": false
4247
}
4348
]
4449
}

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,6 @@ 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-
Azure NetApp Files also supports [breaking file locks](troubleshoot-file-locks.md).
54-
5553
## Why is the `.snapshot` directory not visible in an NFSv4.1 volume, but it's visible in an NFSv3 volume?
5654

5755
By design, the .snapshot directory is never visible to NFSv4.1 clients. By default, the `.snapshot `directory is 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).

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

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,6 @@ Azure NetApp Files supports [`CHANGE_NOTIFY` response](/openspecs/windows_protoc
8080

8181
Azure NetApp Files also supports [`LOCK` response](/openspecs/windows_protocols/ms-smb2/e215700a-102c-450a-a598-7ec2a99cd82c). This response is for the client’s request that comes in the form of a [`LOCK` request](/openspecs/windows_protocols/ms-smb2/6178b960-48b6-4999-b589-669f88e9017d).
8282

83-
Azure NetApp Files also supports [breaking file locks](troubleshoot-file-locks.md).
84-
8583
## What network authentication methods are supported for SMB volumes in Azure NetApp Files?
8684

8785
NTLMv2 and Kerberos network authentication methods are supported with SMB volumes in Azure NetApp Files. NTLMv1 and LanManager are disabled and are not supported.

articles/azure-netapp-files/troubleshoot-file-locks.md

Lines changed: 0 additions & 36 deletions
This file was deleted.
Binary file not shown.

0 commit comments

Comments
 (0)