From: "Yan, Zheng " <yanzheng@21cn.com>
To: "K. Richard Pixley" <rich@noir.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Code bug or data bug?
Date: Tue, 10 Aug 2010 19:12:45 +0800 [thread overview]
Message-ID: <AANLkTikWzo1r5FEsdsTfYCA7c+9Xfhfb9NdbhHuM9_2y@mail.gmail.com> (raw)
In-Reply-To: <4C607F45.3020901@noir.com>
On Tue, Aug 10, 2010 at 6:20 AM, K. Richard Pixley <rich@noir.com> wrot=
e:
> =A0I've just gotten:
>
> rich@diamonds:~$ time sudo /sbin/btrfsck /dev/sda7
> btrfsck: btrfsck.c:585: splice_shared_node: Assertion `!(src =3D=3D
> &src_node->root_cache)' failed.
> Aborted
>
> Does this indicate a coding error in btrfsck or a data error in my fi=
le
> system?
>
> --rich
>
> rich@diamonds:~$ dpkg -l | grep btrfs
> ii =A0btrfs-tools =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
=A0 =A0 =A00.19+20100601-3
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Checksumming Copy on Write Filesy=
stem utilit
> rich@diamonds:~$ uname -a
> Linux diamonds 2.6.32-24-generic-pae #38-Ubuntu SMP Mon Jul 5 10:54:2=
1 UTC
> 2010 i686 GNU/Linux
> rich@diamonds:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: =A0 =A0Ubuntu 10.04.1 LTS
> Release: =A0 =A0 =A0 =A010.04
> Codename: =A0 =A0 =A0 lucid
>
This is a bug in btrfsck.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-08-10 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 22:20 Code bug or data bug? K. Richard Pixley
2010-08-10 11:12 ` Yan, Zheng [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=AANLkTikWzo1r5FEsdsTfYCA7c+9Xfhfb9NdbhHuM9_2y@mail.gmail.com \
--to=yanzheng@21cn.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rich@noir.com \
/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).