diff options
| author | David Sterba <dsterba@suse.cz> | 2013-11-13 18:55:12 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2015-04-22 18:21:48 +0200 |
| commit | 49eab991720a1dbeaffade98fb946f6a22848867 (patch) | |
| tree | f1c86951673c329fd67b9266009f75bd9c361179 /Documentation | |
| parent | c8927d51164f68a5c96090c5f52d8ffa81ec98b7 (diff) | |
btrfs-progs: add zero-log to rescue command
Copy the functionality of standalone btrfs-zero-log to the main tool.
Delete man page for btrfs-zero-log and copy the relevant parts into
btrfs-rescue(8). The standalone utility will be removed later.
Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/Makefile.in | 2 | ||||
| -rw-r--r-- | Documentation/btrfs-rescue.asciidoc | 24 |
2 files changed, 25 insertions, 1 deletions
diff --git a/Documentation/Makefile.in b/Documentation/Makefile.in index 695311dc..0c8b5ba9 100644 --- a/Documentation/Makefile.in +++ b/Documentation/Makefile.in @@ -10,7 +10,6 @@ MAN8_TXT += btrfs-image.asciidoc MAN8_TXT += btrfs-map-logical.asciidoc MAN8_TXT += btrfs-show-super.asciidoc MAN8_TXT += btrfstune.asciidoc -MAN8_TXT += btrfs-zero-log.asciidoc MAN8_TXT += fsck.btrfs.asciidoc MAN8_TXT += mkfs.btrfs.asciidoc @@ -93,6 +92,7 @@ install-man: man $(MV) $(DESTDIR)$(man5dir)/btrfs-mount.5.gz $(DESTDIR)$(man5dir)/btrfs.5.gz $(INSTALL) -m 644 $(GZ_MAN8) $(DESTDIR)$(man8dir) $(LN_S) -f btrfs-check.8.gz $(DESTDIR)$(man8dir)/btrfsck.8.gz + $(LN_S) -f btrfs-rescue.8.gz $(DESTDIR)$(man8dir)/btrfs-zero-log.8.gz uninstall: cd $(DESTDIR)$(man8dir); rm -f btrfs-check.8.gz $(GZ_MAN8) diff --git a/Documentation/btrfs-rescue.asciidoc b/Documentation/btrfs-rescue.asciidoc index e0acf091..32d8a927 100644 --- a/Documentation/btrfs-rescue.asciidoc +++ b/Documentation/btrfs-rescue.asciidoc @@ -40,6 +40,30 @@ assume an answer of 'yes' to all questions. -v:::: verbose mode. +*zero-log* <device>:: +clear out log tree + +*btrfs rescue 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 +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 *zero-log* could be used to clear +the log and the filesystem may be mounted normally again. + EXIT STATUS ----------- *btrfs rescue* returns a zero exit status if it succeeds. Non zero is |