Skip to content

Commit e6e0645

Browse files
authored
Merge pull request #188737 from v-bllyd/patch-27
Update UserErrorFsFreezeFailed error code with Step2
2 parents 9515037 + d8f6b76 commit e6e0645

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

articles/backup/backup-azure-vms-troubleshoot.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,8 @@ The backup operation failed because the VM is in Failed state. For a successful
6868
Error code: UserErrorFsFreezeFailed <br/>
6969
Error message: Failed to freeze one or more mount-points of the VM to take a file-system consistent snapshot.
7070

71+
**Step 1**
72+
7173
* Unmount the devices for which the file system state wasn't cleaned, using the **umount** command.
7274
* Run a file system consistency check on these devices by using the **fsck** command.
7375
* Mount the devices again and retry backup operation.</ol>
@@ -81,6 +83,23 @@ MountsToSkip = /mnt/resource
8183
SafeFreezeWaitInSeconds=600
8284
```
8385

86+
**Step 2**
87+
88+
* Check if there are duplicate mount points present.
89+
90+
Identify the failed to freeze mount points from the extension log file. <br>
91+
For example: /boot, /usr/sap in the below sample output.
92+
```
93+
2017-11-02 11:22:56 Thawing: /boot
94+
2017-11-02 11:22:56 Failed to FITHAW: /boot
95+
2017-11-02 11:22:56 Thawing: /sapshare
96+
2017-11-02 11:22:56 Thawing: /usr/sap
97+
2017-11-02 11:22:56 Failed to FITHAW: /usr/sap
98+
```
99+
100+
On the Linux VM execute 'mount' command and check if the failed mount points have multiple entries. If yes, remove the old entries or rename the mount path and retry the backup operation.
101+
102+
84103
### ExtensionSnapshotFailedCOM / ExtensionInstallationFailedCOM / ExtensionInstallationFailedMDTC - Extension installation/operation failed due to a COM+ error
85104

86105
Error code: ExtensionSnapshotFailedCOM <br/>

0 commit comments

Comments
 (0)