[Feature]: Display custom filesystem labels instead of dm-* device names for additional filesystems

[kc9rqi]

Welcome!

• I have searched open and closed feature requests to make sure this or similar feature request does not already exist.
• This is a feature request, not a bug report or support question.

Component

Hub

Description

When running the Beszel Agent on QNAP (and other Linux systems using device-mapper/LVM), the agent correctly detects additional filesystems mounted under /extra-filesystems, but the Hub displays the kernel device names (dm-0, dm-26, etc.) instead of the custom mount labels.

For example, my configuration includes:

• /share/CACHEDEV1_DATA/.beszel:/extra-filesystems/Main_Storage:ro
• /share/CACHEDEV3_DATA/.beszel:/extra-filesystems/Surveillance:ro
• /share/CACHEDEV5_DATA/.beszel:/extra-filesystems/VM_Storage:ro

The agent logs show the mount labels are already known:
Detected disk name=dm-0 device=/dev/mapper/cachedev1 mount=/extra-filesystems/Main_Storage
Detected disk name=dm-26 device=/dev/mapper/cachedev3 mount=/extra-filesystems/Surveillance
Detected disk name=dm-39 device=/dev/mapper/cachedev5 mount=/extra-filesystems/VM_Storage

However, the Hub displays:
DM-0
DM-26
DM-39

Requested Enhancement:

For filesystems mounted under /extra-filesystems, display the custom mount label (e.g. Main_Storage, Surveillance, VM_Storage) instead of the kernel dm-* device name. If that's not possible, displaying the mapper device name (cachedev1, cachedev3, etc.) would also be more user-friendly than dm-*.

Motivation / Use Case

Using the mount label would:

• Make the dashboard much easier to understand at a glance.
• Eliminate the need to remember or document which dm-* device corresponds to which storage pool.
• Avoid confusion if device-mapper numbers change after a reboot or storage reconfiguration.
• Allow users to assign meaningful names such as Media, Backups, VM Storage, or Surveillance.
• Improve the experience on NAS platforms (QNAP, Synology), Proxmox, and other Linux systems that use LVM/device-mapper.

The agent already knows the mount label (mount=/extra-filesystems/...), so this wold be a UI/display enhancement rather than a detection issue.

[svenvg93]

Thanks for the detailed report! This is actually already supported

The agent supports a __CustomName suffix on the folder name under /extra-filesystems. Any bind-mount folder named <anything>__<CustomName> will show CustomName in the Hub instead of the raw device name (dm-0, etc.).

For your case, you'd rename your bind-mount targets like this:

/share/CACHEDEV1_DATA/.beszel:/extra-filesystems/Main_Storage__Main_Storage
/share/CACHEDEV3_DATA/.beszel:/extra-filesystems/Surveillance__Surveillance
/share/CACHEDEV5_DATA/.beszel:/extra-filesystems/VM_Storage__VM_Storage

The part before __ can be anything (it's just used as a fallback device key); the part after __ becomes the display label shown in the Hub.
It must be a double underscore (__), not a single _ — the parser splits on __ specifically, so a single underscore is just treated as part of the device name and won't trigger custom naming.