On Sun, 2016-09-04 at 05:33 +0000, Paul Jones wrote: > The errors are wrong. I nearly ruined my filesystem a few days ago by > trying to repair similar errors, thankfully all seems ok. > Check again with btrfs-progs 4.6.1 and see if the errors go away, > mine did. > See open bug https://bugzilla.kernel.org/show_bug.cgi?id=155791 for > more details.
Thanks for the pointer :) I can at least confirm that my system seems to work normal, scrub didn't bring any errors either, nor are there any kernel messages... The interesting thing... I have some pretty large btrfs on those 8TiB seagate disks (nearly full with some million files)... which I have also scanned with v4.7... and no errors. Only my system fs seems to be "affected". Well it's not my first case of false positives in btrfs check (https:// www.mail-archive.com/linux-btrfs@vger.kernel.org/msg48325.html)... so I was more relaxed this time (at least a bit ;-) ). Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
