diff options
Diffstat (limited to 'Documentation/btrfs-zero-log.txt')
-rw-r--r-- | Documentation/btrfs-zero-log.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/btrfs-zero-log.txt b/Documentation/btrfs-zero-log.txt index a8e4dd34..0a8d3e33 100644 --- a/Documentation/btrfs-zero-log.txt +++ b/Documentation/btrfs-zero-log.txt @@ -7,17 +7,17 @@ btrfs-zero-log - clear out log tree SYNOPSIS -------- -'btrfs-zero-log' <dev> +*btrfs-zero-log* <dev> DESCRIPTION ----------- -'btrfs-zero-log' will remove the log tree if log tree is corrupt, which will +*btrfs-zero-log* will remove the log tree if log tree is corrupt, which will allow you to mount the filesystem again. The common case where this happens has been fixed a long time ago, so it is unlikely that you will see this particular problem. -One can determine whether 'btrfs-zero-log' is needed according to the kernel +One can determine whether *btrfs-zero-log* is needed according to the kernel backtrace: ---- ? replay_one_dir_item+0xb5/0xb5 [btrfs] @@ -29,15 +29,15 @@ backtrace: ? open_ctree+0xff6/0x132c [btrfs] ---- -If the errors are like above, then 'btrfs-zero-log' should be used to clear +If the errors are like above, then *btrfs-zero-log* should be used to clear the log and the filesystem may be mounted normally again. NOTE: If you use btrfs as the root filesystem, you may want to include -'btrfs-zero-log' into initramdisk if the log problems hits you often. +*btrfs-zero-log* into initramdisk if the log problems hits you often. EXIT STATUS ----------- -'btrfs-zero-log' will return 0 if no error happened. +*btrfs-zero-log* will return 0 if no error happened. Other exit code means some problems happened. AUTHOR |