Re: mount BTRFS filesystems created with 3.8+ under 2.6.32 kernels ?
From: Jason Vas Dias
Date: Mon Sep 22 2014 - 14:07:45 EST
Of course the solution was to have created the filesystem in the first
place with
'mkfs.btrfs -O ^extref' . Found this after some more googling ...
Shouldn't this be the default ?
Regards,
Jason
On 9/22/14, Jason Vas Dias <jason.vas.dias@xxxxxxxxx> wrote:
> Good day -
>
> I wonder if there is a GIT repository somewhere with a backport of the
> BTRFS
> kernel modules that will allow BTRFS filesystems created with a 3.8 kernel
> to
> be mounted on a 2.6.32+ kernel .
>
> When I try this, the 2.6.32 kernel crashes with the message :
> 'BTRFS: couldn't mount because of unsupported optional features (40)'
> ( kernel-2.6.32-431.29.2.el6.x86_64 from RHEL 6.4+ ).
>
> The same filesystem mounts fine under Oracle EL6 which now comes with
> kernel-uek 3.8+ . Has anyone tried to backport the 3.8 BTRFS
> capabilities to 2.6.32 ,
> or is there any way I can remove "Option 40" to get it to mount
> without crashing ?
> It is a very small BTRFS filesystem with a root filesystem and a few
> snapshots.
> I did not specify any BTRFS options in :
> $ mkfs.btrfs /dev/sda9;
> ... # mount on /mnt/btr & create some files
> $ btrfs subvolume snapshot -r /mnt/btr /mnt/btr/root-0
> $ btrfs subvolume snapshot /mnt/btr /mnt/btr/root-w-0
> Now I can mount /dev/sda9 under any 3.8+ kernel, but not under 2.6.32 .
>
> Thanks in advance for any replies,
> Best Regards, Jason Vas Dias
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/