Joseph fbacik of Fedora announced on the developer's email list that the default use of the btrfs File System feature was postponed to Fedora17. The reason for the delay is very simple because BTRFS's error checking tool btrfsck was not available before the ora16 feature was frozen, and the performance problem has been plagued by BTRFS. At the same time, some BTRFS features still need to wait until the Linux3.2 kernel can catch up. With careful and comprehensive consideration, Joseph F
Joseph Bacik of Fedora announced on the developer's email list that the default use of the btrfs File System feature was postponed to Fedora 17.
The reason for the delay is very simple because BTRFS's error checking tool btrfsck was not available before the Fedora 16 feature was frozen, and performance problems have been plaguing BTRFS. At the same time, some BTRFS features still need to wait until the Linux 3.2 kernel can catch up. With careful and comprehensive consideration, Joseph F Bacik decided to postpone this feature to Fedora 17. He said they have tried their best to work diligently, but still cannot make BTRFS stable to use. The improvement of some features cannot be completely controlled by him, but it is still necessary to wait for the upstream kernel to review. In addition, he also revealed that btrfsck will be available in a few weeks. It seems that it will take a few weeks to complete. A word is equal. Finally, this feature has been deleted from the Fedora 16 new feature list. Therefore, Fedora 16 still uses EXT4 as the default file system. As for MeeGo, their BTRFS default file system plan remains unchanged.
Together with the previously canceled firewalld, Fedora 16 has canceled two features. The Fedora 16 Go/No-Go online IRC Meeting will be held at on October 11, August 10, which will decide which features will be abandoned if the development progress is not met, it also determines whether the Fedora 16 Alpha is released on time. All features will be developed before the release of Fedora 16 Alpha.