Now that I'm switching from reiserfs on rust to btrfs on ssd, I'm wondering about the autodefrag mount option. The ssds are mid-range (Corsair Neutrons, NOT Neutron GTXs) so fragmented access shouldn't be anything like the problem it is on spinning rust, but I guess I should still keep fragmentation from getting /too/ far out of hand, as AFAIK that increases IOPS and there's obviously a limit on them. Additionally, I suppose the additional metadata bookkeeping could eventually put further stress on btrfs in terms of concurrent ops, etc. As I'm way overprovisioned (by about 100%, give or take depending on whether I decide to lay down a swap/s2d partition or not, s2r works well but s2d hasn't been due to video issues so I haven't been using that anyway, and I'm running 16 gigs RAM w/ half of it empty even of cache most of the time and power is quite stable here, so little real need for s2d /or/ swap), ssd limited write-cycles shouldn't be a big deal either way. So for now I'm mounting with autodefrag, but honestly that's WAAYYY more because I'm still used to thinking about spinning rust that I'm almost afraid to turn it off, than it is about understanding the relative merits either way. So I'm asking, what are other people doing on SSD, why, and are there any papers out there discussing the merits of defrag on mid-range SSDs, with btrfs or in general? SSDs are so new to me I'm having a hard time getting my head turned around to think about them instead of spinning rust. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
