Comment 4 for bug 748340

I've spoke to another user who did not seem to have these issues on the current version so it seems it might be something to do with my particular system..

When I run fsck using the debian experimental version of the userspace tools I get this output:

ubuntu@ubuntu:~$ sudo btrfsck /dev/sda5
fs tree 259 refs 7 not found
 unresolved ref root 261 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 262 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 263 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 264 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 265 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 266 dir 256 index 31 namelen 4 name snap error 600
 unresolved ref root 267 dir 256 index 31 namelen 4 name snap error 600
found 3873710080 bytes used err is 1
total csum bytes: 3517348
total tree bytes: 258281472
total fs tree bytes: 241065984
btree space waste bytes: 70634105
file data blocks allocated: 15013134336
 referenced 4583772160
Btrfs Btrfs v0.19

This is a fairly recent (few days) install, but what I have done so far is taken snapshots of my "/" subvolume via apt-btrfs-snapshot, rolled back to one of these snapshots, and deleted the old "/" subvolume along with some apt-snapshots that I did not use.

So my guess is that btrfs doesnt like that I've removed my original "/" subvolume, which is then what crashes current, and reports the above erros in experimental btrfs-tools.

So updating to the newer version wouldn't make much of a difference in practice, since mountall would still halt on these errors?