On Tue, Jul 07, 2020 at 10:31:32AM -0400, Josef Bacik wrote: > > Soon after, the copy failed: > > [ 2575.931316] BTRFS info (device dm-0): use zlib compression, level 3 > > [ 2575.931329] BTRFS info (device dm-0): disk space caching is enabled > > [ 2575.931343] BTRFS info (device dm-0): has skinny extents > > [ 2577.286749] BTRFS info (device dm-0): bdev /dev/mapper/crypt_bcache0 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 > > You have a corrupt counter here at mount time, does your logs go back far > enough to see where those came in? Thanks, I copied all the logs in the original Email. Here it is all in one swoop: https://pastebin.com/GURufP8w The devices going down and back up is normal, my backup script saw the backup was over (although in that case that's because it failed) and automatically unmounted the filesystem and turned off the drives. I'm not sure how my FS got so corrupted, it's been a while since I've seen damage that bad, especially pretty unexplained like this. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
