On 11/01/2015 04:22 AM, Duncan wrote:
So what btrfs is logging to dmesg on mount here, are the historical error
counts, in this case expected as they were deliberate during your test,
nearly 200K of them, not one or more new errors.
To have btrfs report these at the CLI, use btrfs device stats. To zero
Thanks for clarifying. I forgot to check btrfs dev stats. That explains it.
The 2-drive failure scenario still caused data corruption with 4.3-rc7
though.
Philip
--
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
