From: "K. Richard Pixley" <rich@noir.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Code bug or data bug?
Date: Mon, 09 Aug 2010 15:20:53 -0700 [thread overview]
Message-ID: <4C607F45.3020901@noir.com> (raw)
I've just gotten:
rich@diamonds:~$ time sudo /sbin/btrfsck /dev/sda7
btrfsck: btrfsck.c:585: splice_shared_node: Assertion `!(src ==
&src_node->root_cache)' failed.
Aborted
Does this indicate a coding error in btrfsck or a data error in my file
system?
--rich
rich@diamonds:~$ dpkg -l | grep btrfs
ii btrfs-tools
0.19+20100601-3 Checksumming Copy on
Write Filesystem utilit
rich@diamonds:~$ uname -a
Linux diamonds 2.6.32-24-generic-pae #38-Ubuntu SMP Mon Jul 5 10:54:21
UTC 2010 i686 GNU/Linux
rich@diamonds:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid
next reply other threads:[~2010-08-09 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 22:20 K. Richard Pixley [this message]
2010-08-10 11:12 ` Code bug or data bug? Yan, Zheng
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=4C607F45.3020901@noir.com \
--to=rich@noir.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).