On Sun, Sep 10, 2017 at 01:16:26PM +0000, Josef Bacik wrote: > Great, if the free space cache is fucked again after the next go > around then I need to expand the verifier to watch entries being added > to the cache as well. Thanks,
Well, I copied about 1TB of data, and nothing happened. So it seems clearing it and fsck may have fixed this fault I had been carrying for quite a while. If so, yeah! I'm not sure if this needs a kernel fix to not get triggered and if btrfs check should also be improved to catch this, but hopefully you know what makes sense there. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html