Merge pull request #236107 from netapp-manishc/netapp-manishc-patch-1

Update azure-netapp-files-resource-limits.md

Author: prmerger-automator[bot]

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 02/23/2023
+ms.date: 04/27/2023
 ms.author: anfdocs
 ---
 # Resource limits for Azure NetApp Files
@@ -61,7 +61,7 @@ For limits and constraints related to Azure NetApp Files network features, see [
 
 ## Determine if a directory is approaching the limit size <a name="directory-limit"></a>  
 
-You can use the `stat` command from a client to see whether a directory is approaching the maximum size limit for directory metadata (320 MB).   
+You can use the `stat` command from a client to see whether a directory is approaching the maximum size limit for directory metadata (320 MB). If you reach the maximum size limit for a single directory for Azure NetApp Files, the error `No space left on device` occurs.   
 
 For a 320-MB directory, the number of blocks is 655360, with each block size being 512 bytes.  (That is, 320x1024x1024/512.)  This number translates to approximately 4 million files maximum for a 320-MB directory. However, the actual number of maximum files might be lower, depending on factors such as the number of files with non-ASCII characters in the directory. As such, you should use the `stat` command as follows to determine whether your directory is approaching its limit.