I was looking at Marc's post: http://marc.merlins.org/perso/btrfs/post_2014-03-19_Btrfs-Tips_-Btrfs-Scrub-and-Btrfs-Filesystem-Repair.html and it feels like there isn't exactly a cohesive, overarching vision for repair of a corrupted btrfs filesystem. In other words - I'm an admin cruising along, when the kernel throws some fs corruption error, or for whatever reason btrfs fails to mount. What should I do? Marc lays out several steps, but to me this highlights that there seem to be a lot of disjoint mechanisms out there to deal with these problems; mostly from Marc's blog, with some bits of my own: * btrfs scrub "Errors are corrected along if possible" (what *is* possible?) * mount -o recovery "Enable autorecovery attempts if a bad tree root is found at mount time." * mount -o degraded "Allow mounts to continue with missing devices." (This isn't really a way to recover from corruption, right?) * btrfs-zero-log "remove the log tree if log tree is corrupt" * btrfs rescue "Recover a damaged btrfs filesystem" chunk-recover super-recover How does this relate to btrfs check? * btrfs check "repair a btrfs filesystem" --repair --init-csum-tree --init-extent-tree How does this relate to btrfs rescue? * btrfs restore "try to salvage files from a damaged filesystem" (not really repair, it's disk-scraping) What's the vision for, say, scrub vs. check vs. rescue? Should they repair the same errors, only online vs. offline? If not, what class of errors does one fix vs. the other? How would an admin know? Can btrfs check recover a bad tree root in the same way that mount -o recovery does? How would I know if I should use --init-*-tree, or chunk-recover, and what are the ramifications of using these options? It feels like recovery tools have been badly splintered, and if there's an overarching design or vision for btrfs fs repair, I can't tell what it is. Can anyone help me? Thanks, -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html