diff options
| author | Qu Wenruo <quwenruo@cn.fujitsu.com> | 2014-04-11 10:43:53 +0800 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2014-04-22 14:15:24 +0200 |
| commit | dad1c8ba3a52afd72dd4b6d46b985dac163925bf (patch) | |
| tree | 3aa297d9d2b36b70ec74fbfdec5b7aff7f09813e /Documentation/btrfs-zero-log.txt | |
| parent | 5dbedcc3e01949ae4095714871346509f9c4624d (diff) | |
btrfs-progs: Add explain on btrfs-zero-log.
Add more explain on btrfs-zero-log about when to use it.
Reviewed-by: Marc MERLIN <marc@merlins.org>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'Documentation/btrfs-zero-log.txt')
| -rw-r--r-- | Documentation/btrfs-zero-log.txt | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/Documentation/btrfs-zero-log.txt b/Documentation/btrfs-zero-log.txt index e3041fa4..a8e4dd34 100644 --- a/Documentation/btrfs-zero-log.txt +++ b/Documentation/btrfs-zero-log.txt @@ -17,6 +17,24 @@ 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 +backtrace: +---- +? replay_one_dir_item+0xb5/0xb5 [btrfs] +? walk_log_tree+0x9c/0x19d [btrfs] +? btrfs_read_fs_root_no_radix+0x169/0x1a1 [btrfs] +? btrfs_recover_log_trees+0x195/0x29c [btrfs] +? replay_one_dir_item+0xb5/0xb5 [btrfs] +? btree_read_extent_buffer_pages+0x76/0xbc [btrfs] +? open_ctree+0xff6/0x132c [btrfs] +---- + +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. + EXIT STATUS ----------- 'btrfs-zero-log' will return 0 if no error happened. |