>> TL;DR: ran into some btrfs errors and weird behaviour, but >> things generally seem to work. Just posting some details in >> case it helps devs or other users. [ ... ] I've run into a >> btrfs error trying to do a -j8 build of android on a btrfs >> filesystem exported over NFSv3. [ ... ] I have an NFS server from Btrfs filesystem, and it is mostly read-only and low-use, unlike a massive build, but so far it has worked for me. The issue that was reported a while ago was that the kernel NFS server does not report as errors to clients checksum validation failures, just prints a warning, so for that reason and a few others I switch to the Ganesha NFS server. >From your stack traces I noticed that some go pretty deep so maybe there is an issue with that (but on 'amd64' the kernel stack is much bigger than it used to be on 'i386'). Another possibility is that the volume got somewhat damaged for other reasons (bugs, media errors, ...) and this is have further consequences. BTW 'errno 17' is "File exists", so perhaps there is a race condition over NFS. The bogus files with mode 0 seem to me to be bogus directory entries with no files linked to them, which could be again the result of race conditions. The problems with chunks allocation reported as "WARNING" are unfamiliar to me. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
