Posted Oct 12, 2011 1:45 UTC (Wed) by cmccabe (guest, #60281)
Parent article: Whither btrfsck?
In a lot of ways, filesystem development turns the normal rules of software development on their head.
Normally, you want to push something out the door as early as possible so you can gain more users, more developers, and more features than the competition. This is usually phrased as "release early, release often." Releasing often is also generally thought to make you more responsive to what users want ("agile").
When you're developing a filesystem, you want the wider community to deploy your changes infrequently and only after a lot of testing. You only need to lose someone's data once to lose that user forever-- and probably a lot of his friends. It's much, much more important to have something rock solid than it is to have a lot of features. Filesystems have a fairly well-defined role to play, and user feedback is usually limited to letting you know when you've screwed up, rather than suggesting new features.
I hope btrfsck gets out the door soon! I'd like to see how distributions make use of the new btrfs subvolumes and other features.