systemd tools fail to mount disk images with btrfs filesystems

Bug #2067907 reported by Daan De Meyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Committed
Undecided
Unassigned
Noble
Triaged
Medium
Nick Rosbrook

Bug Description

SRU Justification

[Impact]

In Ubuntu Noble, systemd-repart fail to mount images with btrfs filesystems in them. This is because the kernel removed the "norecovery" mount option which systemd-repart adds in when mounting filesystems from disk images.

Commit which removed "norecovery" in the kernel: https://github.com/torvalds/linux/commit/a1912f712188291f9d7d434fba155461f1ebef66.

[Fix]

The issue was worked around upstream in systemd in https://github.com/systemd/systemd/pull/32892 and https://github.com/systemd/systemd/pull/32948.

[Test]

To reproduce:

git clone https://github.com/systemd/mkosi
cd mkosi
bin/mkosi -d fedora -t disk --tools-tree=default -f
sudo systemd-repart --image mkosi.output/image.raw
The last command will fail with "Failed to mount image: Invalid argument". After backporting the two systemd commits, the last command will succeed.

[Regression Potential]

Low, the systemd commits only change behavior for btrfs filesystems, which are currently not working at all. The commits have been backported to the systemd stable releases and we've had no reports of any issues caused by backporting these commits.

description: updated
Revision history for this message
Nick Rosbrook (enr0n) wrote :

Thanks for filling out the SRU template. I tested this locally and was able to reproduce the bug using your instructions.

I will include this in the next Noble SRU.

Changed in systemd (Ubuntu Noble):
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Nick Rosbrook (enr0n)
tags: added: systemd-sru-next
Revision history for this message
Nick Rosbrook (enr0n) wrote :

These patches are included in v256, which is currently in oracular-proposed, so we just need to upload to noble.

Changed in systemd (Ubuntu):
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.