On Wed, 5 Jul 2017 22:10:35 -0600 Daniel Brady <drbr...@gmail.com> wrote:
> parent transid verify failed Typically in Btrfs terms this means "you're screwed", fsck will not fix it, and nobody will know how to fix or what is the cause either. Time to restore from backups! Or look into "btrfs restore" if you don't have any. In your case it's especially puzzling as the difference in transid numbers is really significant (about 100K), almost like the FS was operating for months without updating some parts of itself -- and no checksum errors either, so all looks correct, except that everything is horribly wrong. This kind of error seems to occur more often in RAID setups, either Btrfs native RAID, or with Btrfs on top of other RAID setups -- i.e. where it becomes a complex issue that all writes to multi devices DO complete IN order, in case of an unclean shutdown. (which is much simpler on a single device FS). Also one of your disks or cables is failing (was /dev/sde on that boot, but may get a different index next boot), check SMART data for it and replace. > [ 21.230919] BTRFS info (device sdf): bdev /dev/sde errs: wr 402545, rd > 234683174, flush 194501, corrupt 0, gen 0 -- With respect, Roman -- 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
