You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Nemo version: 3.8.5
* Is issue with desktop or windowed nemo? Windowed nemo
* Distribution: Arch
* Graphics hardware *and* driver used: irrelevant
* 32 or 64 bit: 64 bit
Issue
Nemo uses the same BTRFS partition label for all of its mounted subvolumes or snapshots.
Also, if multiple subvolumes of the same BTRFS partition get mounted, only one of them is showing its used/overall space bar below it.
I know this issue has to do with the subvolumes which are no real block devices, but it is confusing and annoying in those cases, where you are using BTRFS subvolumes as a replacement for logical block devices.
Here's an example of Nemo's device list showing a single BTRFS partition with the label "media" and five of its mounted subvolumes (ignore the other three regular block devices):
Expected behavior
Having an option to either
hide items of the devices list (then the user can simply use bookmarks)
locally rename items of the devices list (and store this data, based on device UUID and certain mount parameters (subvol or subvolid))
use the subvol path as name, eg. /@foo or /path/to/subvolume instead of the BTRFS label, unless it is not a subvolume or snapshot
Issue
I know this issue has to do with the subvolumes which are no real block devices, but it is confusing and annoying in those cases, where you are using BTRFS subvolumes as a replacement for logical block devices.
Here's an example of Nemo's device list showing a single BTRFS partition with the label "media" and five of its mounted subvolumes (ignore the other three regular block devices):
Expected behavior
Having an option to either
/@foo
or/path/to/subvolume
instead of the BTRFS label, unless it is not a subvolume or snapshotSteps to reproduce
/media
and mount individual subvolumesOther information
Related to #1497
The text was updated successfully, but these errors were encountered: