Skip to content

Commit 4b5ba1c

Browse files
author
Simonx Xu
authored
Merge pull request #8960 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)
2 parents d7be632 + c55078d commit 4b5ba1c

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

support/azure/virtual-machines/linux/linux-recovery-cannot-start-file-system-errors.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,9 @@ ms.topic: troubleshooting
1313
ms.workload: infrastructure-services
1414
ms.tgt_pltfrm: vm-linux
1515
ms.devlang: azurecli
16-
ms.date: 07/19/2022
16+
ms.date: 05/20/2025
1717
ms.author: genli
18+
ms.reviewer: maries, v-weizhu
1819
---
1920
# Troubleshoot Linux virtual machine boot issues due to filesystem errors
2021

@@ -328,11 +329,14 @@ or
328329
mount /home
329330
```
330331

331-
If the journaled changes aren't written when you mount filesystems, use the `-L` flag to discard the journal and mount the filesystem as if all changes are successfully completed. When the `-L` flag is used, data loss will occur because the log shows incomplete file operations are being discarded.
332+
If the journaled changes aren't written when you mount filesystems, use the `-L` flag to discard the journal and mount the filesystem as if all changes are successfully completed.
333+
332334
333335
```bash
334336
xfs_repair -L /dev/rootvg/homelv /recovery
335337
```
338+
> [!CAUTION]
339+
> The `-L` flag forces `xfs_repair` to clean entries in the transaction log journal, which often results in data loss.
336340
337341
### <a id="prevent-boot-failure"></a>Prevent boot failure
338342

0 commit comments

Comments
 (0)