Tomáš Bžatek

> any news on this? No progress on `smartmontools` integration, not on a short-term roadmap for the moment. However I'm working on NVMe support right now which will provide drive...

> > However I'm working on NVMe support right now which will provide drive health information among other stuff. > > Any progress? Yes, please see #975. If you have...

> Check also [smartmontools/smartmontools#133](https://github.com/smartmontools/smartmontools/issues/133) Oh nice, thanks. I'll keep that on my watch list. One thing I was thinking about was SAS drive support in the new `smart` `libblockdev` plugin...

I'm okay with continually refining detection scenarios and always scanning removable media sounds good for now. Plugging removable media in is a user-aware action and if anything goes wrong like...

You can assume that both the `InterfacesAdded` and `PropertiesChanged` signals are valid and can be received in random order, as a result of asynchronous nature of the messaging chain. What's...

Also, could you post `udevadm info /dev/.....`, `blkid` and `lsblk` dumps here related to the block device carrying the UDF filesystem please?

@cmurf, can you please attach `udevadm info --export-db` too? I'm wondering whether there are any `udev` properties specific to `btrfs` multidisk volume.

> (This may not be entirely different from LVM thin pool or Stratis pool as the parent, and its filesystems as children - if this metaphor holds - except in...

Opened https://github.com/kdave/btrfs-progs/issues/302 requesting at least some information published in the udev db. I believe such kind of information should be provided at the right place first as the local storage...

It's more complicated than that. Kernel and udev operates on `major:minor` block device nodes and `/dev/disk/` symlinks are just different representations of the same object. Similarly any reference to a...