Created attachment 1700711 [details] screenshot Description of problem: I installed the btrfs testday (yeah, I'm a bit late) image Fedora-Workstation-Live-x86_64-20200708-btrfsdefault.iso in a VM and chose automatic partitioning, which creates a btrfs filesystem with three subvolumes. I can't see the subvolumes it created using blivet-gui, though. Version-Release number of selected component (if applicable): blivet-gui-2.1.14-2.fc33.noarch How reproducible: Always Steps to Reproduce: 1. Install Fedora with btrfs 2. Open blivet-gui 3. Click on the btrfs volume in the sidebar Actual results: The list of devices in 'logical view' shows only the btrfs volume. Expected results: All the btrfs subvolumes should be listed nested under the btrfs volume. Additional info: If you use blivet-gui to create a new subvolume, it shows up as expected, nested under its btrfs volume, even after applying the change. But if you close and reopen blivet-gui, the newly-created subvolume is no longer visible.
There are actually two "problems" in this issue: 1. The btrfs device must be mounted in order to get the list of subvolumes on it. We mount btrfs devices in Anaconda during the initial storage scan but I've decided to not mount "random" btrfs volumes in blivet-gui so unmounted btrfs volumes are not going to show list subvolumes. I don't want to change this behaviour, users can have multiple btrfs volumes and mounting them could cause other problems. I'll try to think about a way how to show this information in the UI and possibly add some "mount & rescan" option. 2. In your case the device is actually mounted. This is a bug in blivet -- we check for the mountpoint of the volume which is not mounted, but we can use the subvolume mountpoints (e.g. "/home") to run `btrfs subvolume list` and we don't do that right now.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Both "problems" (Comment 1) are still present in Fedora 35.
upstream PR: https://github.com/storaged-project/blivet/pull/1007