Problem/Justification
The SCALE webUI does not include the overall compression ratio in the dashboard, which is information that was previously available in CORE. This is valuable information for monitoring, and available through standard zfs get compressratio from the CLI, but a graphical representation is easier for end-users to quickly verify.
See thread: Compression Ratio vanished in SCALE?
Impact
Advantage:
Displaying the compression and/or deduplication ratios as a “data reduction ratio” allows for easy identification of data savings and whether or not a particular dataset is benefiting from these features.
Disadvantage:
Additional UI space will need to be allocated depending on the type of information displayed. Some existing information might need to be removed or put a level deeper.
User Story
The Datasets panel can show the Compression Ratio, for example in the place of the atime setting.
Absolutely, voted.
Having at-a-glance info for space allocation savings is ubiquitous across almost every storage vendor implementation I’ve used. The example for compression is perfect.
Logistically, it would probably be easier to do block cloning and dedupe at the pool level tho, since per-dataset accounting for those features don’t currently exist in ZFS IIRC.
e.g.
root@rawht[~]# zpool get bcloneratio,dedupratio ice
NAME PROPERTY VALUE SOURCE
ice bcloneratio 2.00x -
ice dedupratio 1.00x -
root@rawht[~]#
No sure if this is the right place to mention this but I’ve just discovered that in SCALE you also can’t see if a dataset is READONLY or not which once again in CORE was visible from the top dataset menu. This is really helpful to see at a glance especially on replicated systems. Can we add that to this feature request @HoneyBadger or do you think that would need a separate one?
“Thanks for the bug report. This is not a bug, but an intentional change between versions. Potential feature changes and requests are not handled via our forum’s feature request category.
About the Feature Requests category - README First”
This was part of a cleanup for moving to this “feature request” forum category.
Best to create a separate thread for “readonly” visibility. It was removed to simplify and declutter the interface, but if people need it, we need to find a mechanism.
