Sorry I need to include a patch I sent recently to the list. Those
errors are bogus, btrfsck just needs to be taught about our special
space cache inodes. I'll pull that into fedora. You are right, you
don't need to run btrfsck on boot, just if you run into issues.
Thanks,
Josef
On Thu, Apr 12, 2012 at 6:13 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
On Apr 11, 2012, at 12:00 PM, Josef Bacik wrote:
> Got it all updated, it's in koji, 0.19-18 is what you want. Thanks,
Thanks Josef. This is now available with a yum update and has fixed the problem. However,
this is what I get as a result.
I'm under the impression that a btrfsck isn't needed if there are no mount
errors. Yet in this case there are no mount errors in dmesg, yet btrfsck says there are
errors. Expected, or not? And is this better taken to the btrfs list?
[root@f17v chris]# btrfsck /dev/sdb4
checking extents
checking fs roots
root 5 inode 18446744073709551604 errors 2000
root 5 inode 18446744073709551605 errors 1
found 6472544256 bytes used err is 1
total csum bytes: 5872152
total tree bytes: 459329536
total fs tree bytes: 426516480
btree space waste bytes: 134110780
file data blocks allocated: 15564447744
referenced 6255255552
Btrfs Btrfs v0.19
Chris Murphy
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel