Skip to content

Commit 6accd15

Browse files
committed
50 tib limit
1 parent 308247a commit 6accd15

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The following table describes resource limits for Azure NetApp Files:
2929
| Maximum size of a single capacity pool | 1000 TiB | Yes |
3030
| Minimum size of a single regular volume | 100 GiB | No |
3131
| 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 |
3333
| Large volume size increase | 30% of lowest provisioned size | Yes |
3434
| Maximum size of a single large volume | 500 TiB | No |
3535
| 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
101101
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.
102102

103103
>[!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.
105105
> 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.
106106
107107
**For [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes):**
108108

109109
| Volume size (quota) | Automatic readjustment of the `maxfiles` limit |
110110
| - | - |
111-
| > 100 TiB | 2,550,135,120 |
111+
| > 50 TiB | 2,550,135,120 |
112112
113113
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.
114114

articles/azure-netapp-files/large-volumes-requirements-considerations.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ The following requirements and considerations apply to large volumes. For perfor
2525

2626
* Existing regular volumes can't be resized over 100 TiB.
2727
* You can't convert regular Azure NetApp Files volumes to large volumes.
28-
* You must create a large volume at a size greater than 50 TiB. A single volume can't exceed 500 TiB.
29-
* You can't resize a large volume to less than 50 TiB.
30-
* You can only resize a large to be volume up to 30%, of lowest provisioned size.
28+
* You must create a large volume at a size greater than 100 TiB. A single volume can't exceed 500 TiB.
29+
* You can't resize a large volume to less than 100 TiB.
30+
*
3131
* Large volumes are currently not supported with Azure NetApp Files backup.
3232
* Large volumes aren't currently supported with cross-region replication.
3333
* You can't create a large volume with application volume groups.
@@ -37,9 +37,9 @@ The following requirements and considerations apply to large volumes. For perfor
3737

3838
| Capacity tier | Volume size (TiB) | Throughput (MiB/s) |
3939
| --- | --- | --- |
40-
| Standard | 100 to 500 | 1,600 |
41-
| Premium | 100 to 500 | 6,400 |
42-
| Ultra | 100 to 500 | 10,240 |
40+
| Standard | 50 to 500 | 1,600 |
41+
| Premium | 50 to 500 | 6,400 |
42+
| Ultra | 50 to 500 | 10,240 |
4343

4444
* Large volumes aren't currently supported with standard storage with cool access.
4545

0 commit comments

Comments
 (0)