From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-zero-log (v 0.20-rc1) corrupted double linked list.
Date: Thu, 17 Oct 2013 15:57:16 -0700 [thread overview]
Message-ID: <20131017225716.GG5390@merlins.org> (raw)
In-Reply-To: <20131017212924.GE5390@merlins.org>
On Thu, Oct 17, 2013 at 02:29:24PM -0700, Marc MERLIN wrote:
> I asked the debian maintainer to add btrfs-zero-log to the initramfs since I
> unfortunately have to use it from time to time.
>
> It still fixes the problem for me when btrfs won't mount, but it errors at
> the end.
>
> See screenshot
I was able to run it through some OCR which will allow this to get indexed.
BusyBox v1.19.3 (Debian 1:1.19.3—5) built-in shell (ash)
Enter 'help' for a list of built—in commands.
/bin/sh: can't access tty; job control turned off
(initramfs) btrfs—zero—log /dev/mapper/cryptroot
Check tree block failed, want=32927752192, have=11251525731377178129
Check tree block failed, want=32927752192, have=11251525731377178129
Check tree block failed. want=32927752192, have=6210801847113163713
Check tree block failed, want=32927752192, have=62108018171§3163713
Check tree block failed, want=32927752192, have=6210801847113163713
read block failed check_tree_block
*** Error in ‘btrfs—zero—log': corrupted double—linked list: 0x008000008171c6b0 ***
(numbers are off, see screenshot for real numbers)
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/
prev parent reply other threads:[~2013-10-17 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 21:29 btrfs-zero-log (v 0.20-rc1) corrupted double linked list Marc MERLIN
2013-10-17 22:57 ` Marc MERLIN [this message]
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=20131017225716.GG5390@merlins.org \
--to=marc@merlins.org \
--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).