Public bug reported: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014.
A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs-progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs eoan ftbfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848935 Title: Ubuntu Eoan 10.10 fails to boot after updating from 19.04 disco with btrfs Status in linux package in Ubuntu: New Bug description: Current eoan v5.3.0 kernel has a much more strict tree checker for btrfs and may fail to mount the file system in case there are bad inode generations after an upgrade. This may be the case on file systems created before 2014. A a result of failing to mount the user will land in the initramfs busybox. Manually trying to mount will display the failing inodes. Unfortunately the built-in (in initramfs) btrfs checker from btrfs- progs 5.2.1 can not repair this problem. That is related to this patch for btrfs-progs 5.3-rc1: https://lore.kernel.org/linux- btrfs/eb937822-50fb-1515-9407-f5a4e4b06...@gmail.com/T/#mfa319e441efe5a3b66955891ed61ed47e33bf543 As a work around after the upgrade the user should boot the old (disco) kernel and should be made aware not to remove this. As a more permanent resolution then linux-oem can be installed. In principle a script can be devised to save the failing inodes with new, or when available btrfs-progs could be updated to 5.3 to repair the file system. In any case it should be considered that the failing inodes might be present on multiple snapshots of the fs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
