From: Marc MERLIN <marc@merlins.org>
To: Mihail Zaporozhets <kamheric@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs restore
Date: Thu, 21 Aug 2014 18:52:16 -0700 [thread overview]
Message-ID: <20140822015216.GE3875@merlins.org> (raw)
In-Reply-To: <loom.20140821T061503-238@post.gmane.org>
On Thu, Aug 21, 2014 at 05:52:01AM +0000, Mihail Zaporozhets wrote:
> # btrfs-zero-log /dev/sda1
> warning devid 5 not found already
> Check tree block failed, want=16845270495232, have=0
> read block failed check_tree_block
> Couldn't read tree root
You may be hitting the same problem I was a week back. See the thread
that says "btrfs-zero-log fails, can't mount FS"
Download the source for btrfs-progs, and apply this patch from Chris:
diff --git a/disk-io.c b/disk-io.c
index 8db0335..d9a8e19 100644
--- a/disk-io.c
+++ b/disk-io.c
@@ -911,13 +911,13 @@ int btrfs_setup_all_roots(struct btrfs_fs_info *fs_info, u64 root_tree_bytenr,
return -EIO;
}
fs_info->csum_root->track_dirty = 1;
-
+#if 0
ret = find_and_setup_log_root(root, fs_info, sb);
if (ret) {
printk("Couldn't setup log root tree\n");
return -EIO;
}
-
+#endif
fs_info->generation = generation;
fs_info->last_trans_committed = generation;
if (extent_buffer_uptodate(fs_info->extent_root->node) &&
Or if you're desparate and want a binary, I'll Email you one directly
(not that you should run a binary you got from someone via Email as
root, so it's only if you're desperate)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-08-22 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 5:52 btrfs restore Mihail Zaporozhets
2014-08-22 1:52 ` Marc MERLIN [this message]
2014-08-22 2:36 ` Marc MERLIN
2014-08-22 8:39 ` Mihail Zaporozhets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140822015216.GE3875@merlins.org \
--to=marc@merlins.org \
--cc=kamheric@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).