So you zero'd the log? Why? You need to slow down and stop making changes to your file system unless you hate your data and want to lose it. The log is there to help protect your data, you don't zero the log except under very specific situations, none of which appear to apply to your situation. 'btrfs check' is safe, --repair may or may not be safe, you didn't say what version of btrfs-progs you're using, I would consider 4.14.1 at the oldest, it should be straightforward with any distro to get something relatively new, maybe from a testing repo. Current is 4.16. And good god don't use --init-extent-tree, that's a hammer. The absolute safest way to troubleshoot Btrfs problems is using newer kernel versions, even though 4.15 is not old, there are still tons of bug fixes in every release. Suspicious items from your dmesg: [95639.492347] BTRFS error (device dm-11): pending csums is 44810240 [95639.492791] BTRFS error (device dm-11): cleaner transaction attach returned -30 [95639.609171] BTRFS error (device dm-11): open_ctree failed [96614.907963] BTRFS info (device dm-11): disk space caching is enabled [96614.907965] BTRFS info (device dm-11): has skinny extents [96615.207692] BTRFS info (device dm-11): bdev /dev/mapper/em3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3 [96615.207702] BTRFS info (device dm-11): bdev /dev/mapper/em5 errs: wr 164286, rd 3444262, flush 2110, corrupt 3, gen 181 OK so it's a multiple device Btrfs volume, and you have one device missing a metric done of reads and writes and flushes, with a few corruptions and generation mismatches. What's wrong with /dev/mapper/em5? Have you done any troubleshooting to figure out what that problem is? Because Btrfs can't fix it, and it can't make up for it. That looks like the device was missing for a long time, and writes were only going to em3. So what's the backstory? Your very first task right now is to mount ro, and update your backups. Don't do anything else until you've done that. It's a testimony to Btrfs that this file system mounts at all, even ro, so take advantage of this fact before you can't mount it anymore. -- Chris Murphy -- 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
