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/maxfiles-concept.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: concept-article
8
-
ms.date: 07/04/2025
8
+
ms.date: 10/13/2025
9
9
ms.author: anfdocs
10
10
# Customer intent: "As a cloud storage administrator, I want to understand the `maxfiles` limits for Azure NetApp Files, so that I can effectively manage volume capacity and avoid 'out of space' errors when creating new files."
11
11
---
12
12
# Understand `maxfiles` limits in Azure NetApp Files
13
13
14
-
Azure NetApp Files volumes have a value called `maxfiles` that refers to the maximum number of files and folders (also known as inodes) a volume can contain. The `maxfiles` limit for an Azure NetApp Files volume is based on the size (quota) of the volume, where the service dynamically adjusts the `maxfiles` limit for a volume based on its provisioned size and uses the following guidelines.
14
+
Azure NetApp Files volumes have a value called `maxfiles` that refers to the maximum number of files and folders (also known as inodes) a volume can contain. The `maxfiles` limit for an Azure NetApp Files volume is based on the size (quota) of the volume. The service dynamically adjusts the `maxfiles` limit for a volume based on its provisioned size and uses the following guidelines.
15
15
16
16
- For regular volumes less than or equal to 683 GiB, the default `maxfiles` limit is 21,251,126.
17
17
- For regular volumes greater than 683 GiB, the default `maxfiles` limit is approximately one file (or inode) per 32 KiB of allocated volume capacity up to a maximum of 2,147,483,632.
@@ -47,14 +47,14 @@ To see the `maxfiles` allocation for a specific volume size, check the **Maximum
47
47
:::image type="content" source="./media/azure-netapp-files-resource-limits/maximum-number-files.png" alt-text="Screenshot of volume overview menu." lightbox="./media/azure-netapp-files-resource-limits/maximum-number-files.png":::
48
48
49
49
>[!NOTE]
50
-
>The maximum number of files metric is reported against the `maxfiles` account quota limit. The metric in Azure Mmonitor might reflect fewer files than metrics provided by the operating system mounting the volume. This behavior is expected.
50
+
>The maximum number of files metric is reported against the `maxfiles` account quota limit. The metric in Azure Monitor might reflect fewer files than metrics provided by the operating system mounting the volume. This behavior is expected.
51
51
52
52
When the `maxfiles` limit is reached, clients receive "out of space" messages when attempting to create new files or folders. Adjusting your quota based on this information can create greater inode availability.
53
53
54
54
>[!NOTE]
55
-
>If you want to increase the `maxfiles` limit, you must increase the corresponding volume size accordingly. To increase the `maxfiles` limit, contact Microsoft technical support.
55
+
>If you want to increase the `maxfiles` limit for a volume, you must increase the volume's size. If your volume is at the [maximum size](azure-netapp-files-resource-limits.md) and you still need to increase the `maxfiles` limit, contact Microsoft technical support.
56
56
57
-
You can't set `maxfiles` limits for data protection volumes via a quota request. Azure NetApp Files automatically increases the `maxfiles` limit of a data protection volume to accommodate the number of files replicated to the volume. When a failover happens on a data protection volume, the `maxfiles` limit remains the last value before the failover. In this situation, you can submit a `maxfiles`[quota request](azure-netapp-files-resource-limits.md#request-limit-increase) for the volume.
57
+
You can't set `maxfiles` limits for data protection volumes with a quota request. Azure NetApp Files automatically increases the `maxfiles` limit of a data protection volume to accommodate the number of files replicated to the volume. When a failover happens on a data protection volume, the `maxfiles` limit remains the last value before the failover. In this situation, you can submit a `maxfiles`[quota request](azure-netapp-files-resource-limits.md#request-limit-increase) for the volume.
0 commit comments