On Fri, Mar 29, 2013 at 1:21 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > Chris Murphy wrote: >> On Mar 29, 2013, at 12:04 AM, cwillu <cwillu@xxxxxxxxxx> wrote: >> >>> 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. >> >> mkfs.btrfs -l 8192 >> >> That is not mountable by 3.8.5. I get: >> >> [ 252.870733] btrfs: disk space caching is enabled >> [ 252.870740] btrfs flagging fs with big metadata feature >> [ 252.874944] btrfs: failed to recover relocation >> [ 252.885186] btrfs: open_ctree failed >> >> That's definitely not expected. > > mkfs.btrfs -l 8192 with kernel 3.9.0 creates a file system mountable by 3.9.0 and only 3.9.0 (so far). And while there's no error making such a file system with other kernels, they won't mount the resulting file system. > I'm seeing something similar. Using the current master branch of btrfs-progs (https://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git, top commit 7854c8b667654502f69e05584729146a06827bc6 "Btrfs-progs: give restore a list roots option"), if I run 'mkfs.btrfs -f /dev/<device>' on a 3.7.x vintage kernel, the mkfs operation is successful, but I can't mount the partition. I am successful on a 3.8.x vintage kernel or testing the _rc code for 3.9. -- 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
