'\" t .\" Title: btrfs-rescue .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] .\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 09/22/2016 .\" Manual: Btrfs Manual .\" Source: Btrfs v4.7.3 .\" Language: English .\" .TH "BTRFS\-RESCUE" "8" "09/22/2016" "Btrfs v4\&.7\&.3" "Btrfs Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" btrfs-rescue \- Recover a damaged btrfs filesystem .SH "SYNOPSIS" .sp \fBbtrfs rescue\fR \fI\fR \fI\fR .SH "DESCRIPTION" .sp \fBbtrfs rescue\fR is used to try to recover a damaged btrfs filesystem\&. .SH "SUBCOMMAND" .PP \fBchunk\-recover\fR [options] \fI\fR .RS 4 Recover the chunk tree by scanning the devices .sp \fBOptions\fR .PP \-y .RS 4 assume an answer of \fIyes\fR to all questions\&. .RE .PP \-v .RS 4 verbose mode\&. .RE .PP \-h .RS 4 help\&. .RE .RE .if n \{\ .sp .\} .RS 4 .it 1 an-trap .nr an-no-space-flag 1 .nr an-break-flag 1 .br .ps +1 \fBNote\fR .ps -1 .br .sp Since \fBchunk\-recover\fR will scan the whole device, it will be \fBVERY\fR slow especially executed on a large device\&. .sp .5v .RE .PP \fBsuper\-recover\fR [options] \fI\fR .RS 4 Recover bad superblocks from good copies\&. .sp \fBOptions\fR .PP \-y .RS 4 assume an answer of \fIyes\fR to all questions\&. .RE .PP \-v .RS 4 verbose mode\&. .RE .RE .PP \fBzero\-log\fR \fI\fR .RS 4 clear the filesystem log tree .RE .sp This command will clear the filesystem log tree\&. This may fix a specific set of problem when the filesystem mount fails due to the log replay\&. See below for sample stacktraces that may show up in system log\&. .sp The common case where this happens has been fixed a long time ago, so it is unlikely that you will see this particular problem, but the utility is kept around\&. .if n \{\ .sp .\} .RS 4 .it 1 an-trap .nr an-no-space-flag 1 .nr an-break-flag 1 .br .ps +1 \fBNote\fR .ps -1 .br .sp clearing the log may lead to loss of changes that were made since the last transaction commit\&. This may be up to 30 seconds (default commit period) or less if the commit was implied by other filesystem activity\&. .sp .5v .RE .sp One can determine whether \fBzero\-log\fR is needed according to the kernel backtrace: .sp .if n \{\ .RS 4 .\} .nf ? 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] .fi .if n \{\ .RE .\} .sp If the errors are like above, then \fBzero\-log\fR should be used to clear the log and the filesystem may be mounted normally again\&. The keywords to look for are \fIopen_ctree\fR which says that it\(cqs during mount and function names that contain \fIreplay\fR, \fIrecover\fR or \fIlog_tree\fR\&. .SH "EXIT STATUS" .sp \fBbtrfs rescue\fR returns a zero exit status if it succeeds\&. Non zero is returned in case of failure\&. .SH "AVAILABILITY" .sp \fBbtrfs\fR is part of btrfs\-progs\&. Please refer to the btrfs wiki \m[blue]\fBhttp://btrfs\&.wiki\&.kernel\&.org\fR\m[] for further details\&. .SH "SEE ALSO" .sp \fBmkfs\&.btrfs\fR(8), \fBbtrfs\-scrub\fR(8), \fBbtrfs\-check\fR(8)