Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Dave <dave@thekilempire.com>
To: Ken D'Ambrosio <ken@jots.org>
Cc: "Fajar A. Nugraha" <list@fajar.net>, linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount (or, why not to work late at night).
Date: Tue, 1 Nov 2011 11:06:05 -0400	[thread overview]
Message-ID: <20111101150605.GA28280@hendrix.borisch.local> (raw)
In-Reply-To: <7d421a89143f5c4811d64e08c6820c29@www.jots.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Oct 27, 2011 at 08:32:09PM -0400, Ken D'Ambrosio wrote:
> root@ubuntu:/tmp/btrfs-progs# ./btrfs-zero-log /dev/sda1
> parent transid verify failed on 100695031808 wanted 217713 found 217732
> parent transid verify failed on 100695031808 wanted 217713 found 217732
> parent transid verify failed on 100695031808 wanted 217713 found 217732
> btrfs-zero-log: disk-io.c:413: find_and_setup_root: Assertion '!(!root->node)'
> failed.

This is the same bullshit I dealt with back in August.  In short, your data is
likely fine.  btrfs is preventing you from accessing your data because there is
something wrong with the csum tree.  My solution was to create a custom kernel
which ignored all checksums.  I was then able to mount the filesystem read-only
and copy data to another volume.

http://thread.gmane.org/gmane.comp.file-systems.btrfs/12344

I've had this happen to me on two occasions.  The first time was after a hard
reboot.  The second was on a totally different machine at a different geographic
location, which occurred after nothing more than a reboot.
- -- 
- -=[dave]=-

Entropy isn't what it used to be.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iF4EAREIAAYFAk6wCtwACgkQXM0u5ajNnCj7bQD+LWnK+rF6t3ajkeFfFYfap8eA
eaeRWtH/uVkO3RMTFEMA/1H9aBSDWxfhtFd6a11KRYm5MYYonYtfMtpDqxgl7H0k
=MNIf
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2011-11-01 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  0:32 Unable to mount (or, why not to work late at night) Ken D'Ambrosio
2011-10-28  0:49 ` dima
2011-10-28  0:57 ` Fajar A. Nugraha
2011-10-28 11:57   ` Stephane CHAZELAS
2011-11-01 15:06 ` Dave [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-27 15:22 Ken D'Ambrosio
2011-10-27 16:47 ` Helmut Hullen
2011-10-27 22:32 ` Fajar A. Nugraha

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=20111101150605.GA28280@hendrix.borisch.local \
    --to=dave@thekilempire.com \
    --cc=ken@jots.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    /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