On Thu, May 19, 2011 at 2:26 PM, Josef Bacik <[email protected]> wrote: > > Yeah so this is a crappy thing about btrfs, we need to cache free space, so we > have to run these threads to read the extent tree to put together the free > space > cache. You can get around this by moving to a new kernel and mounting with > > -o space_cache > > This will enable the space caching feature, so you will get those threads > once, > but then every time after that it will be fast and you shouldn't see those > threads at all. Its a disk format change, so you only have to mount -o > space_cache once and then it will be permament. Thanks, > > Josef > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html >
Out of curiosity, why isn't this done automatically as opposed to having to mount with the space_cache option? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
