On Thu, Mar 28, 2013 at 11:41 PM, Chris Murphy <li...@colorremedies.com> wrote: > Creating a btrfs file system using > btrfs-progs-0.20.rc1.20130308git704a08c-1.fc19, and either kernel > 3.6.10-4.fc18 or 3.9.0-0.rc3.git0.3.fc19, makes a file system that cannot be > mounted by kernel 3.6.10-4.fc18. It can be mounted by kernel 3.8.4. I haven't > tested any other 3.8, or any 3.7 kernels. > > Is this expected? > > dmesg reports: > [ 300.014764] btrfs: disk space caching is enabled > [ 300.024137] BTRFS: couldn't mount because of unsupported optional features > (40). > [ 300.034148] btrfs: open_ctree failed
commit 1a72afaa "btrfs-progs: mkfs support for extended inode refs" unconditionally enables extended irefs (which permits more than 4k links to the same inode). It's the right default imo, but there probably should have been a mkfs option to disable it. -- 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
