linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-zero-log (v 0.20-rc1) corrupted double linked list.
Date: Thu, 17 Oct 2013 14:29:24 -0700	[thread overview]
Message-ID: <20131017212924.GE5390@merlins.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

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

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/  

[-- Attachment #2: linkedlist.jpg --]
[-- Type: image/jpeg, Size: 26201 bytes --]

             reply	other threads:[~2013-10-17 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 21:29 Marc MERLIN [this message]
2013-10-17 22:57 ` btrfs-zero-log (v 0.20-rc1) corrupted double linked list Marc MERLIN

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=20131017212924.GE5390@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).