Christoph Anton Mitterer posted on Fri, 13 Nov 2015 04:57:29 +0100 as excerpted: > As I've said I have these two 8TiB disks... one which is basically the > master with loads of precious data, the other being a backup from the > master, regularly created with incremental btrfs send/receive. 8 TiB disks -- are those the disk-managed SMR "archive" disks I've read about on a number of threads? If so, that hardware is almost certainly the cause, as they're known to be problematic on current kernels. While most filesystems (all?) will apparently go corrupt on them, it can remain invisible corruption for quite some time on many of them, but btrfs with its checksums and etc will tend to show up the problems far sooner, and there have been at least 2-3 threads on the problem already, on this list. As I don't have any of those disks here I've been following the threads from a bit of a distance and haven't kept up with the full details, but I do know there's an active bugzilla.kernel.org bug open on the problem, and that the problem was first exposed by a commit that was supposed to help /support/ this sort of drive. Rolling it back does seem to help. I don't recall what kernel that commit landed in, but it was definitely after 3.16, so if that's what you were originally running, the problem wouldn't have shown up right away, until you upgraded to a kernel with the offending commit. For more than that, you'll either need to wait until someone following a bit closer (possibly affected by the problem) posts a better followup, or find the other threads in the list archive, that discuss the issue. You shouldn't have to go back more than a couple weeks or so, and it's very likely in the last week, so almost certainly in this month's posts, if you're checking a list archive on the web. -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
