Description of problem: Before upgrade of btrfs-progs, using btrfs-progs-6.0.2-1.fc37.x86_64: $ sudo btrfs subvolume list -u / ID 256 gen 148466 top level 5 uuid 57760724-47c5-b748-b49c-ae5f1c41e14a path root ID 257 gen 148466 top level 5 uuid d9e13a78-41bd-4b42-8a60-10b15ecae5c1 path home [...] After upgrade of btrfs-progs to btrfs-progs-6.1-1.fc37.x86_64: $ sudo btrfs subvolume list -u / ID 256 gen 148478 top level 5 uuid - path root ID 257 gen 148478 top level 5 uuid - path home [...] Where did the UUID go? No reboot in between, just dnf upgrade. Version-Release number of selected component (if applicable): btrfs-progs-6.1-1.fc37.x86_64 How reproducible: 100%. Steps to Reproduce: 1. Pretty clear from the above, I would think. 2. 3. Actual results: ID 256 gen 148478 top level 5 uuid - path root ID 257 gen 148478 top level 5 uuid - path home Expected results: ID 256 gen 148466 top level 5 uuid 57760724-47c5-b748-b49c-ae5f1c41e14a path root ID 257 gen 148466 top level 5 uuid d9e13a78-41bd-4b42-8a60-10b15ecae5c1 path home Additional info: My btrbk backups are failing with the message that there is no subvolume UUID.
Fixed by this series: https://patchwork.kernel.org/project/linux-btrfs/list/?series=707080 I hope David should do a minor release to fix this problem.
(In reply to Qu Wenruo from comment #1) > Fixed by this series: > > https://patchwork.kernel.org/project/linux-btrfs/list/?series=707080 > > I hope David should do a minor release to fix this problem. This patch does indeed seem to fix the problem. I have applied it locally.
FEDORA-2022-e7a28a653b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e7a28a653b
FEDORA-2022-e538a8b8e7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e538a8b8e7
FEDORA-2022-e7a28a653b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-e538a8b8e7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.