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-resource-limits.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The following table describes resource limits for Azure NetApp Files:
29
29
| Maximum size of a single capacity pool | 1000 TiB | Yes |
30
30
| Minimum size of a single regular volume | 100 GiB | No |
31
31
| Maximum size of a single regular volume | 100 TiB | No |
32
-
| Minimum size of a single [large volume](large-volumes-requirements-considerations.md)|50 TiB| No |
32
+
| Minimum size of a single [large volume](large-volumes-requirements-considerations.md)|102,401 GiB| No |
33
33
| Large volume size increase | 30% of lowest provisioned size | Yes |
34
34
| Maximum size of a single large volume | 500 TiB | No |
35
35
| Maximum size of a single file | 16 TiB | No |
@@ -101,14 +101,14 @@ For volumes 100 TiB or under, if you've allocated at least 5 TiB of quota for a
101
101
For volumes 100 TiB or under, you can increase the `maxfiles` limit up to 531,278,150 if your volume quota is at least 25 TiB.
102
102
103
103
>[!IMPORTANT]
104
-
> When files or folders are allocated to an Azure NetApp Files volume, they count against the `maxfiles` limit. If a file or folder is deleted, the internal data structures for `maxfiles` allocation remain the same. For instance, if the files used in a volume increase to 63,753,378 and 100,000 files are deleted, the `maxfiles` allocation will remain at 63,753,378.
104
+
> When files or folders are allocated to an Azure NetApp Files volume, they count against the `maxfiles` limit. If a file or folder is deleted, the internal data structures for `maxfiles` allocation remain the same. For instance, if the files used in a volume increase to 63,753,378 and 100,000 files are deleted, the `maxfiles` allocation remains at 63,753,378.
105
105
> Once a volume has exceeded a `maxfiles` limit, you cannot reduce volume size below the quota corresponding to that `maxfiles` limit even if you have reduced the actual used file count. For example, the `maxfiles` limit for a 2 TiB volume is 63,753,378. If you create more than 63,753,378 files in that volume, the volume quota cannot be reduced below its corresponding index of 2 TiB.
| Volume size (quota) | Automatic readjustment of the `maxfiles` limit |
110
110
| - | - |
111
-
| > 100 TiB | 2,550,135,120 |
111
+
| > 50 TiB | 2,550,135,120 |
112
112
113
113
You can increase the `maxfiles` limit beyond 2,550,135,120 using a support request. For every 2,550,135,120 files you increase (or a fraction thereof), you need to increase the corresponding volume quota by 120 TiB. For example, if you increase `maxfiles` limit from 2,550,135,120 to 5,100,270,240 files (or any number in between), you need to increase the volume quota to at least 240 TiB.
0 commit comments