Public bug reported:
= Description =
On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem,
root subvolume (subvol=@) is always mounted as read only. There is a kernel
flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by
script /usr/sbin/update-grub during every kernel update. Only home subvolume
(@home) is actually mounted as rw according to fstab which is correct.
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS
(subvolumes @ and @home are created)
2. Launch the kernel via the default grub entry
= Expected Results =
root / should be mounted as rw (mount -v | grep @), there should be no (ro)
flag on /proc/cmdline
= Actual Results =
in grub.cfg:
linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=xxxx-xxxx-...
rootflags=subvol=@ ro quiet splash $vt_handoff
in /proc/cmdline:
BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic
root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet
splash vt.handoff=7
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1968094
Title:
BTRFS root subvolume @ mounted always as readonly (... ro
rootflags=subvol=@ ...) on Jammy
Status in network-manager package in Ubuntu:
New
Bug description:
= Description =
On Ubuntu Jammy Jellyfish (beta 220330) installed fully on BTRFS filesystem,
root subvolume (subvol=@) is always mounted as read only. There is a kernel
flag (ro) appended to GRUB configuration file /boot/grub/grub.cfg created by
script /usr/sbin/update-grub during every kernel update. Only home subvolume
(@home) is actually mounted as rw according to fstab which is correct.
Image: Jammy Beta (220330)
= Steps to Reproduce =
1. Install Jammy Beta (220330) on PC w. EFI and select FS root (/) to BTRFS
(subvolumes @ and @home are created)
2. Launch the kernel via the default grub entry
= Expected Results =
root / should be mounted as rw (mount -v | grep @), there should be no (ro)
flag on /proc/cmdline
= Actual Results =
in grub.cfg:
linux /@/boot/vmlinuz-5.15.0-23-generic root=UUID=xxxx-xxxx-...
rootflags=subvol=@ ro quiet splash $vt_handoff
in /proc/cmdline:
BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic
root=UUID=981dd6de-02fc-41a9-9e2a-09dbbc776b2b ro rootflags=subvol=@ quiet
splash vt.handoff=7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1968094/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
