Skip to content

Commit d68fa34

Browse files
authored
Merge pull request #8139 from MicrosoftDocs/main
Auto push to live 2025-02-03 18:00:02
2 parents f149e8d + cfc5460 commit d68fa34

4 files changed

Lines changed: 506 additions & 102 deletions

File tree

support/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot problems connecting to and accessing SMB Azure file sh
44
services: storage
55
ms.service: azure-file-storage
66
ms.custom: sap:Connectivity, devx-track-azurepowershell, linux-related-content
7-
ms.date: 01/30/2025
7+
ms.date: 02/04/2025
88
ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal
99
---
1010
# Troubleshoot Azure Files connectivity and access issues (SMB)
@@ -266,7 +266,7 @@ To learn more, see [Prerequisites for mounting an Azure file share with Linux an
266266

267267
##### Cause 2: Virtual network or firewall rules are enabled on the storage account, or port 445 is blocked
268268

269-
If virtual network (VNET) and firewall rules are configured on the storage account, network traffic will be denied access unless the client IP address or virtual network is allowed access. In addition, if your company or ISP is blocking port 445 outbound, you won't be able to mount the share.
269+
If virtual network (VNET) and firewall rules are configured on the storage account, network traffic will be denied access unless the client IP address or virtual network is allowed access. In addition, if your company or ISP blocks port 445 outbound, you won't be able to mount the share.
270270

271271
##### Solution for cause 2
272272

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues with cloud tiering in an Azure File Sync
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 01/28/2025
7+
ms.date: 02/04/2025
88
ms.author: kendownie
99
ms.reviewer: vritikanaik, v-weizhu
1010
ms.custom: sap:File Sync
@@ -102,7 +102,7 @@ If content doesn't exist for the error code, follow the general troubleshooting
102102
| 0x80c83007 | -2134364153 | ECS_E_STORAGE_ERROR | The file failed to tier due to an Azure storage issue. | If the error persists, open a support request. |
103103
| 0x800703e3 | -2147023901 | ERROR_OPERATION_ABORTED | The file failed to tier because it was recalled at the same time. | No action required. The file will be tiered when the recall completes and the file is no longer in use. |
104104
| 0x80c80264 | -2134375836 | ECS_E_GHOSTING_FILE_NOT_SYNCED | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
105-
| 0x80070001 | -2147024895 | ERROR_INVALID_FUNCTION | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running or because the file has an extension of `.sid`. | Security identifier (.sid) files can't be read by the storage sync service, so they can't be tiered to the cloud. If the file doesn't have an extension of `.sid`, you can resolve this issue by opening an elevated command prompt and running the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
105+
| 0x80070001 | -2147024895 | ERROR_INVALID_FUNCTION | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running or because the file has a .sid extension. | Security identifier (.sid) files can't be read by the storage sync service, so they can't be tiered to the cloud. If the file doesn't have a .sid extension, you can resolve this issue by opening an elevated command prompt and running the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
106106
| 0x80c86041 | -2134351807 | ECS_E_AFS_FILTER_NOT_LOADED | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run this command `fltmc load storagesync`. <br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
107107
| 0x80070070 | -2147024784 | ERROR_DISK_FULL | The file failed to tier due to insufficient disk space on the volume where the server endpoint is located. | To resolve this issue, free at least 100 MiB of disk space on the volume where the server endpoint is located. |
108108
| 0x80070490 | -2147023728 | ERROR_NOT_FOUND | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |

0 commit comments

Comments
 (0)