https://bugzilla.redhat.com/show_bug.cgi?id=1033764
Can someone tell me if I should be able to create a system using the extlinux bootloader with /boot on a regular partition formated ext4 and the rootfs ("/") on a btrfs subvol?
This is no show stopper if it should work, but it does not work.
Gene
On Nov 26, 2013, at 1:41 PM, Gene Czarcinski gczarcinski@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1033764
Can someone tell me if I should be able to create a system using the extlinux bootloader with /boot on a regular partition formated ext4 and the rootfs ("/") on a btrfs subvol?
This is no show stopper if it should work, but it does not work.
It should work, I suspect rootflags= is missing from the kernel param line in extlinux.conf as it's the kernel's job to mount btrfs rootfs, not the bootloader. This might be freezeexception worthy.
Chris Murphy
On 11/26/2013 04:01 PM, Chris Murphy wrote:
On Nov 26, 2013, at 1:41 PM, Gene Czarcinski gczarcinski@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1033764
Can someone tell me if I should be able to create a system using the extlinux bootloader with /boot on a regular partition formated ext4 and the rootfs ("/") on a btrfs subvol?
This is no show stopper if it should work, but it does not work.
It should work, I suspect rootflags= is missing from the kernel param line in extlinux.conf as it's the kernel's job to mount btrfs rootfs, not the bootloader. This might be freezeexception worthy.
If this is not working, I cannot get too excited about it because (obviously) nobody is using it.
Now, this is from a ext4 system with extlinux that works:
label Fedora (3.11.8-300.fc20.x86_64) 20 (Heisenbug) kernel /boot/vmlinuz-3.11.8-300.fc20.x86_64 append root=UUID=92fd6132-b765-4475-a754-b0b34e25fd2e vconsole.font=latarcyrheb-sun16 vconsole.keymap=us psmouse.proto=imps rhgb quiet LANG=en_US.UTF-8 initrd /boot/initramfs-3.11.8-300.fc20.x86_64.img
and here is the one from the /boot on ext4 but rootfs on btrfs:
label Fedora (3.11.8-300.fc20.x86_64) kernel /vmlinuz-3.11.8-300.fc20.x86_64 append vconsole.keymap=us vconsole.font=latarcyrheb-sun16 psmouse.proto=imps root=UUID=909a8e5a-2b60-4b76-b665-6e5167c7e4fc rhgb quiet LANG=en_US.UTF-8 initrd /initramfs-3.11.8-300.fc20.x86_64.img
Look pretty much the same to me.
The error message said something about initrd-switch-root failing. Sorry, this is out of my past experience.
Again, I do not see this as any type of blocker. It needs to get fixed but how much of this is really used? Except for nuts like me and Chris? ;)
Gene
On Nov 26, 2013, at 3:16 PM, Gene Czarcinski gczarcinski@gmail.com wrote:
and here is the one from the /boot on ext4 but rootfs on btrfs:
label Fedora (3.11.8-300.fc20.x86_64) kernel /vmlinuz-3.11.8-300.fc20.x86_64 append vconsole.keymap=us vconsole.font=latarcyrheb-sun16 psmouse.proto=imps root=UUID=909a8e5a-2b60-4b76-b665-6e5167c7e4fc rhgb quiet LANG=en_US.UTF-8 initrd /initramfs-3.11.8-300.fc20.x86_64.img
Look pretty much the same to me.
And that's the problem. With btrfs, anaconda needs to include the kernel param rootflags=subvol=root in order to get the kernel to know it needs to use the root subvol as rootfs. It does this for GRUB2 but for some reason isn't doing it for extlinux. So it's an anaconda bug.
I bet dollars to donuts if you add that parameter to your extlinux.conf that it will then boot.
The error message said something about initrd-switch-root failing. Sorry, this is out of my past experience.
Yes it's imploding because it can't find rootfs.
Again, I do not see this as any type of blocker. It needs to get fixed but how much of this is really used? Except for nuts like me and Chris? ;)
Not a blocker, freeze exception. If devs get the time to fix it, it'll get fixed. Might be mattdm who fixes it so I'll reproduce, propose the FE and cc Matt.
Chris Murphy
On 11/26/2013 05:24 PM, Chris Murphy wrote:
On Nov 26, 2013, at 3:16 PM, Gene Czarcinski gczarcinski@gmail.com wrote:
and here is the one from the /boot on ext4 but rootfs on btrfs:
label Fedora (3.11.8-300.fc20.x86_64) kernel /vmlinuz-3.11.8-300.fc20.x86_64 append vconsole.keymap=us vconsole.font=latarcyrheb-sun16 psmouse.proto=imps root=UUID=909a8e5a-2b60-4b76-b665-6e5167c7e4fc rhgb quiet LANG=en_US.UTF-8 initrd /initramfs-3.11.8-300.fc20.x86_64.img
Look pretty much the same to me.
And that's the problem. With btrfs, anaconda needs to include the kernel param rootflags=subvol=root in order to get the kernel to know it needs to use the root subvol as rootfs. It does this for GRUB2 but for some reason isn't doing it for extlinux. So it's an anaconda bug.
I bet dollars to donuts if you add that parameter to your extlinux.conf that it will then boot.
The error message said something about initrd-switch-root failing. Sorry, this is out of my past experience.
Yes it's imploding because it can't find rootfs.
Again, I do not see this as any type of blocker. It needs to get fixed but how much of this is really used? Except for nuts like me and Chris? ;)
Not a blocker, freeze exception. If devs get the time to fix it, it'll get fixed. Might be mattdm who fixes it so I'll reproduce, propose the FE and cc Matt.
You got it. Added the rootflags=subvol=root1 and it came up with no problems. First time I have seen anaconda forget this.
Gene
-
Chris Murphy -
Gene Czarcinski