Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Dave <dave@thekilempire.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed.
Date: Tue, 2 Aug 2011 14:16:31 -0400	[thread overview]
Message-ID: <20110802181630.GA5026@hendrix.borisch.local> (raw)
In-Reply-To: <20110802144452.GA15647@hendrix.borisch.local>

OK so on further investigation, I can see that btrfs-debug-tree is failing on:
ret = find_and_setup_root(tree_root, fs_info, BTRFS_CSUM_TREE_OBJECTID, csum_root);
(line 750 or so)

But the same call with extent_root and dev_root as arguments are successful.
Would this indicate that some branch on the tree holding the file checksums is
what's broken?  And if so, is there a way to mount the filesystem as read-only
while ignoring the checksum tree altogether?  Does this even make sense?

  reply	other threads:[~2011-08-02 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 14:44 disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed Dave
2011-08-02 18:16 ` Dave [this message]
2011-08-03 13:26   ` Dave

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=20110802181630.GA5026@hendrix.borisch.local \
    --to=dave@thekilempire.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