Skip to content

Commit 58deb50

Browse files
authored
Refine Azure File Share capacity troubleshooting steps
1 parent 5de1128 commit 58deb50

1 file changed

Lines changed: 9 additions & 17 deletions

File tree

support/azure/azure-storage/files/performance/files-troubleshoot-performance.md

Lines changed: 9 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -239,31 +239,23 @@ It's possible you're experiencing throttling, and your requests are being sent t
239239

240240
Ensure your app is within the [Azure Files scale targets](/azure/storage/files/storage-files-scale-targets#azure-files-scale-targets). If you're using standard Azure file shares, consider switching to premium.
241241

242-
### Cause 3: **Identifying the Largest Files or Directories within Azure File Share**
242+
### Cause 3: Azure File Share reaches capacity
243243

244-
When Azure file shares are approaching their capacity, it's essential for customers to identify the largest files and directories to optimize storage. This process provides detailed insights into the specific files and folders consuming the most space.
245-
246-
### Solution
247-
248-
To get a comprehensive view of storage usage across the entire share, mount the root of the share. This allows for a thorough inspection of file and directory sizes. From the root of the file share, execute the following commands to identify the largest files and directories:
244+
When the Azure file share is close to reaching its capacity, it's important to identify the largest files and directories to optimize storage. This step helps you understand which files and folders are using the most space.
245+
246+
### Workaround
247+
248+
To get a comprehensive view of storage usage across the entire share, mount the root of the share. This allows for a thorough inspection of file and directory sizes. From the root of the file share, run the following commands to identify the largest files and directories:
249249

250250

251-
```shell
251+
```bash
252252
cd /path/to/mount/point
253253
du -ah --max-depth=1 | sort -rh | head -n 20
254254
```
255-
256255

257-
This command will display the top 20 largest files and directories in descending order of size, providing a clear overview of storage consumption.
256+
This command will display the top 20 largest files and directories in descending order of size. It provides a clear overview of storage consumption.
258257

259-
### Workaround
260-
- If mounting the root of the share is not feasible, consider using Azure Storage Explorer or other third-party tools to analyze storage usage.
261-
- These tools can provide similar insights into file and directory sizes without the need to mount the share directly.
262-
263-
264-
265-
266-
258+
If you can't mount the root of the share, use Azure Storage Explorer or a third-party tool to analyze storage usage. These tools provide similar insights into file and directory sizes without requiring you to mount the share.
267259

268260
## Throughput on Linux clients is lower than that of Windows clients
269261

0 commit comments

Comments
 (0)