On 05/11/2016 11:29 AM, Adam Borowski wrote:
This happens a lot on real-world loads. The issue is apparently benign,
as unsaved pending checksums are moot when the ship^Winode is going down
anyway. Thus, no need to cause panic in users.
I've retained the warning in CONFIG_BTRFS_ASSERT builds, as this shouldn't
happen. I've replaced the no longer helpful register+stack dump with a
printk that mentions the device affected.
Chris is working on fixing the problem, and these are real issues, we
need to not hide them behind config options. Thanks,
Josef
--
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
