On Tue, Sep 13, 2011 at 01:01:00PM -0500, Jeff Putney wrote: > Isn't it about time to make some hard decisions about btrfsck? Three > years is enough time to go without this type of functionality in a > modern filesystem, especially given btrfs's fragility in the face of > power failures. So this criticism is well deserved. I'm juggling a ton of btrfs todos and not doing a great job at communicating the current status of things. Currently we have a pretty big queue of changes that I'm integrating for 3.2, and I had to delay btrfsck again so that I could start testing things. The merge window is pretty short, and there are some fantastic changes that deserve to go in. Inside of Oracle, we've decided to make btrfs the default filesystem for Oracle Linux. This is going into beta now and we'll increase our usage of btrfs in production over the next four to six months. This is a really big step forward, but it doesn't cover btrfs in database workloads (since we recommend asm for that outside of the filesystem). What this means is that absolutely cannot move forward without btrfsck. RH, Fujitsu, SUSE and others have spent a huge amount of time on the filesystem and it is clearly time to start putting it into customer hands. So over the next two weeks I'm juggling the merge window and the fsck release. My goal is to demo fsck at linuxcon europe. Thanks again for all of your patience and help with Btrfs! -chris -- 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