Rich Freeman posted on Sat, 25 Oct 2014 21:41:27 -0400 as excerpted: > However, i'm still getting "bdev /dev/sdb2 errs: wr 0, rd 1361, flush 0, > corrupt 0, gen 0" in my dmesg logs. I have tried scrubbing the device > with no errors found.
Note that error counts do /not/ reset at boot. The counts are therefore since either the last mkfs, or the last time the error counts were reset manually, and if you know you've had errors (as you did here), all you need to do is take note of the count and ensure it's not increasing unexpectedly. Meanwhile, btrfs device stats can be used to print the error counts on demand and its -z option resets them after that print, thus being the manual reset I mentioned above. So chances are those read errors are the same ones you had previously. As long as the number isn't increasing, you're not registering any further errors. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
