Skip to content

Commit 58e34ab

Browse files
Merge pull request #239802 from jeffpatt24/patch-2
Update files-whats-new.md
2 parents 4f80907 + c2816cd commit 58e34ab

File tree

3 files changed

+12
-3
lines changed

3 files changed

+12
-3
lines changed

articles/storage/files/files-troubleshoot-smb-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -562,7 +562,7 @@ In Linux, you might receive an error message that resembles the following:
562562

563563
You've reached the upper limit of concurrent open handles that are allowed for a file or directory.
564564

565-
There is a quota of 2,000 open handles on a single file or directory. When you have 2,000 open handles, an error message is displayed that says the quota is reached.
565+
Azure Files supports 10,000 open handles on the root directory and 2,000 open handles per file and directory within the share.
566566

567567
#### Solution
568568

articles/storage/files/files-whats-new.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,14 @@ Azure Files is updated regularly to offer new features and enhancements. This ar
1515
## What's new in 2023
1616

1717
### 2023 quarter 2 (April, May, June)
18+
#### Azure Files scalability improvement for Azure Virtual Desktop and other workloads is generally available
19+
Azure Files has increased the root directory handle limit per share from 2,000 to 10,000 for standard and premium file shares. This improvement benefits applications that keep an open handle on the root directory. For example, Azure Virtual Desktop with FSLogix profile containers now supports 10,000 active users per share (5x improvement).
20+
21+
Note: The number of active users supported per share is dependent on the applications that are accessing the share. If your applications are not opening a handle on the root directory, Azure Files can support more than 10,000 active users per share.
22+
23+
The root directory handle limit has been increased in all regions and applies to all existing and new file shares. For more information about Azure Files scale targets, see: [Azure Files scalability and performance targets](storage-files-scale-targets.md).
24+
25+
1826
#### Geo-redundant storage for large file shares is in public preview
1927

2028
Azure Files geo-redundancy for large file shares preview significantly improves capacity and performance for standard SMB file shares when using geo-redundant storage (GRS) and geo-zone redundant storage (GZRS) options. The preview is only available for standard SMB Azure file shares. For more information, see [Azure Files geo-redundancy for large file shares preview](geo-redundant-storage-for-large-file-shares.md).

articles/storage/files/storage-files-scale-targets.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,13 +82,14 @@ File scale targets apply to individual files stored in Azure file shares.
8282
| Maximum concurrent request rate | 1,000 IOPS | Up to 8,000<sup>1</sup> |
8383
| Maximum ingress for a file | 60 MiB/sec | 200 MiB/sec (Up to 1 GiB/s with SMB Multichannel)<sup>2</sup> |
8484
| Maximum egress for a file | 60 MiB/sec | 300 MiB/sec (Up to 1 GiB/s with SMB Multichannel)<sup>2</sup> |
85-
| Maximum concurrent handles per file, directory, and share root<sup>3</sup> | 2,000 handles | 2,000 handles |
85+
| Maximum concurrent handles for root directory<sup>3</sup> | 10,000 handles | 10,000 handles |
86+
| Maximum concurrent handles per file and directory<sup>3</sup> | 2,000 handles | 2,000 handles |
8687

8788
<sup>1 Applies to read and write I/Os (typically smaller I/O sizes less than or equal to 64 KiB). Metadata operations, other than reads and writes, may be lower. These are soft limits, and throttling can occur beyond these limits.</sup>
8889

8990
<sup>2 Subject to machine network limits, available bandwidth, I/O sizes, queue depth, and other factors. For details see [SMB Multichannel performance](./storage-files-smb-multichannel-performance.md).</sup>
9091

91-
<sup>3 Azure Files supports 2,000 open handles per share, and in practice can go higher. However, if an application keeps an open handle on the root of the share, the share root limit will be reached before the per-file or per-directory limit is reached.</sup>
92+
<sup>3 Azure Files supports 10,000 open handles on the root directory and 2,000 open handles per file and directory within the share. The number of active users supported per share is dependent on the applications that are accessing the share. If your applications are not opening a handle on the root directory, Azure Files can support more than 10,000 active users per share.</sup>
9293

9394
## Azure File Sync scale targets
9495
The following table indicates which targets are soft, representing the Microsoft tested boundary, and hard, indicating an enforced maximum:

0 commit comments

Comments
 (0)