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: support/azure/azure-storage/files/performance/files-troubleshoot-performance.md
+9-17Lines changed: 9 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,31 +239,23 @@ It's possible you're experiencing throttling, and your requests are being sent t
239
239
240
240
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.
241
241
242
-
### Cause 3: **Identifying the Largest Files or Directories within Azure File Share**
242
+
### Cause 3: Azure File Share reaches capacity
243
243
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:
249
249
250
250
251
-
```shell
251
+
```bash
252
252
cd /path/to/mount/point
253
253
du -ah --max-depth=1 | sort -rh | head -n 20
254
254
```
255
-
256
255
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.
258
257
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.
267
259
268
260
## Throughput on Linux clients is lower than that of Windows clients
0 commit comments