Btrfs volumes are like NFS or tmpfs, a superblock without any associated
device. The behavior is expected and intentional.
Btrfs volumes might be constructed of many volumes, there cannot be the
concept of *that* device, like the "dumb" filesystems use.
There is no way for the udev API to find out which device is behind
a btrfs volume. Btrfs specific command need to be used to determine that,
no generic interface exists for that task.
Btrfs volumes are like NFS or tmpfs, a superblock without any associated
device. The behavior is expected and intentional.
Btrfs volumes might be constructed of many volumes, there cannot be the
concept of *that* device, like the "dumb" filesystems use.
There is no way for the udev API to find out which device is behind
a btrfs volume. Btrfs specific command need to be used to determine that,
no generic interface exists for that task.