You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-faqs.md
+22-2Lines changed: 22 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.devlang: na
15
15
ms.topic: conceptual
16
-
ms.date: 03/06/2020
16
+
ms.date: 03/13/2020
17
17
ms.author: b-juche
18
18
---
19
19
# FAQs About Azure NetApp Files
@@ -55,7 +55,7 @@ All Azure NetApp Files volumes are encrypted using the FIPS 140-2 standard. All
55
55
56
56
Key management for Azure NetApp Files is handled by the service. A unique XTS-AES-256 data encryption key is generated for each volume. An encryption key hierarchy is used to encrypt and protect all volume keys. These encryption keys are never displayed or reported in an unencrypted format. Encryption keys are deleted immediately when a volume is deleted.
57
57
58
-
Support for user-managed keys (Bring Your Own Keys) using Azure Dedicated HSM is available on a controlled basis in the US East, US West2, and US South Central regions. Customer can request access at [email protected], and as capacity is available, requests will be approved.
58
+
Support for user-managed keys (Bring Your Own Keys) using Azure Dedicated HSM is available on a controlled basis in the US East, US West2, and US South Central regions. You can request access at **[email protected]**. As capacity is available, requests will be approved.
59
59
60
60
### Can I configure the NFS export policy rules to control access to the Azure NetApp Files service mount target?
61
61
@@ -159,6 +159,26 @@ Azure NetApp Files provides capacity pool and volume usage metrics. You can also
159
159
160
160
No. Azure NetApp Files is not supported by Azure Storage Explorer.
161
161
162
+
### How do I determine if a directory is approaching the limit size?
163
+
164
+
You can use the `stat` command from a client to see whether a directory is approaching the maximum size limit (320 MB).
165
+
166
+
For a 320 MB directory, the number of blocks is 655360, with each block size being 512 bytes. (That is, 320x1024x1024/512.)
0 commit comments