Skip to contentSkip to conversation

Code bug or data bug?

DISCUSSION K. Richard Pixley 2 participants 2 messages Aug 9, 2010 – Aug 10, 2010 Btrfs file system

lore
Share & tools
lore
#0 lore 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
#1 lore raw

On Tue, Aug 10, 2010 at 6:20 AM, K. Richard Pixley <[email protected]> wrot= e:

Quoted 8 lines

=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

Quoted 6 lines

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

Quoted 1 line

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Checksumming Copy on Write Filesy=

stem utilit

Quoted 2 lines
rich@diamonds:~$ uname -a
Linux diamonds 2.6.32-24-generic-pae #38-Ubuntu SMP Mon Jul 5 10:54:2=

1 UTC

Quoted 8 lines

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html