Chris Murphy

[udevadminfo.txt](https://github.com/storaged-project/udisks/files/5301083/udisks.802-udevadminfo.txt)

I mentioned in [gvfs#519](https://gitlab.gnome.org/GNOME/gvfs/-/issues/519) but forgot to mention here; seems that udisksd is being asked to mount by /dev node rather than by fs UUID. At least from the man...

> The new kernel mount API could possibly take slightly different approach, however this needs to be reflected in `libmount` public API. I was thinking of the clients, e.g. gvfs,...

> It's the combination of the filesystem usability flag and duplicate UUID that causes the problem. ~~Would it help having ID_FS_USAGE=btrfs? Or does that just make things more complicated?~~ Nevermind,...

Another possibility is to use mount --uuid instead of device node, anytime the UUID fs type is Btrfs, and filter for additional instances (i.e. only mount a UUID one time...

During boot, a udev Btrfs rule uses BTRFS_IOC_DEVICES_READY to check if all devices are present and prevents systemd from trying to mount a Btrfs volume if all of its devices...

Is it possible to reassign this to libblockdev? Or does it need a new issue opened?

>device numbers are not used anymore even for single device filesystems (as it's often difficult or impossible to distiguish how many components are needed prior to mounting) Each member device...

> Structure of an active mount looks to be exposed on `/sys/fs/btrfs//devices` which is exactly I was looking for. I forgot to mention the sysfs stuff, sorry. The problem is...

[coredumpctl-gdb-stacktrace.txt](https://github.com/AltraMayor/f3/files/6713450/coredumpctl-gdb-stacktrace.txt)