Re: btrfs -- what happens when a checksum fails on a single disk?

Tim Connors wrote:

I also worry about the really bad fragmentation of files. Sounds like a fundamental problem if you want to have writes that are friendly to SSD, you're going to have reads that are very much unfriendly to spinning rust.

If you are referring to -o ssd and -o ssd_thingo, they are off by default. The former is enabled automatically iff the kernel detects a non-rotating disk[0]. The latter is a variant that "ought to" deal better with shittier FTLs (like, mtdblock / USB key shitty; as opposed to Intel SSDs). [0] not the case for G.Skill Falcon II 64G, apparently.