I noticed my data partition had some inode inconsistencies, so I run btrfs check --repair. However, it did nothing and errors are still there: [root@sandiskFit juha]# btrfs check --repair /dev/mapper/HDD--total-data enabling repair mode Fixed 0 roots. Checking filesystem on /dev/mapper/HDD--total-data UUID: 3dfb375d-6a7c-47a5-a134-179585941d51 checking extents checking free space cache cache and super generation don't match, space cache will be invalidated checking fs roots root 5 inode 2207209 errors 400, nbytes wrong root 5 inode 2256086 errors 400, nbytes wrong root 5 inode 2278303 errors 400, nbytes wrong root 5 inode 2282131 errors 400, nbytes wrong root 5 inode 2288244 errors 400, nbytes wrong root 5 inode 2307687 errors 400, nbytes wrong found 123129939084 bytes used err is 1 total csum bytes: 443189672 total tree bytes: 1094713344 total fs tree bytes: 501399552 total extent tree bytes: 81510400 btree space waste bytes: 164316106 file data blocks allocated: 617742684160 referenced 521218134016 Btrfs v3.17 [root@sandiskFit juha]# btrfs check /dev/mapper/HDD--total-data Checking filesystem on /dev/mapper/HDD--total-data UUID: 3dfb375d-6a7c-47a5-a134-179585941d51 checking extents checking free space cache cache and super generation don't match, space cache will be invalidated checking fs roots root 5 inode 2207209 errors 400, nbytes wrong root 5 inode 2256086 errors 400, nbytes wrong root 5 inode 2278303 errors 400, nbytes wrong root 5 inode 2282131 errors 400, nbytes wrong root 5 inode 2288244 errors 400, nbytes wrong root 5 inode 2307687 errors 400, nbytes wrong found 206299866321 bytes used err is 1 total csum bytes: 443189672 total tree bytes: 1094713344 total fs tree bytes: 501399552 total extent tree bytes: 81510400 btree space waste bytes: 164316106 file data blocks allocated: 617742684160 referenced 521218134016 Btrfs v3.17 I am using Btrfs tools v3.17 and kernel 3.17 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html