Sometimes btrfs scrub status reports that is not running when it still is. I think this a cosmetic bug. And I believe this is related to the scrub completing on some drives before others in a multi-drive btrfs filesystem that is not well balanced.
Based on `iostat 1` activity the last drive in the btrfs filesystem was still being scrubbed at the time I copied the output below, you can see the total bytes scrubbed is increasing despite showing as "not running". The last drive being scrubbed was not the device identified when you list mount points with `mount`: # date ; echo ; btrfs scrub status /mcmedia/ Wed Jan 14 15:20:18 EST 2015 scrub status for 94b3345e-2589-423c-a228-d569bf94ab58 scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136912 seconds, not running total bytes scrubbed: 23.05TiB with 513 errors error details: verify=19 csum=494 corrected errors: 512, uncorrectable errors: 1, unverified errors: 0 # date ; echo ; btrfs scrub status /mcmedia/ Wed Jan 14 15:21:25 EST 2015 scrub status for 94b3345e-2589-423c-a228-d569bf94ab58 scrub started at Tue Jan 13 01:18:22 2015, interrupted after 136982 seconds, not running total bytes scrubbed: 23.06TiB with 513 errors error details: verify=19 csum=494 corrected errors: 512, uncorrectable errors: 1, unverified errors: 0 # uname -a Linux mcplex 3.18.2-gentoo #1 SMP Mon Jan 12 10:24:25 EST 2015 x86_64 Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz GenuineIntel GNU/Linux # btrfs --version Btrfs v3.18.1 -- Sandy McArthur Jr "He who dares not offend cannot be honest." - Thomas Paine -- 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
