On 24/03/14 20:19, Duncan wrote: > Martin posted on Mon, 24 Mar 2014 19:47:34 +0000 as excerpted: > >> Possible fix: >> >> btrfs checks the ratio of filesize versus number of fragments and for a >> bad ratio either: [...] > >> 3: Automatically defragments the file. > > See the autodefrag mount option. > > =:^)
Thanks for that! So... https://btrfs.wiki.kernel.org/index.php/Mount_options #### autodefrag (since [kernel] 3.0) Will detect random writes into existing files and kick off background defragging. It is well suited to bdb or sqlite databases, but not virtualization images or big databases (yet). Once the developers make sure it doesn't defrag files over and over again, they'll move this toward the default. #### Looks like I might be a good test case :-) What's the problem for big images or big databases? What is considered "big"? Thanks, Martin -- 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
