-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZPool properties are not parsable #25
Comments
It's a mistake in the call to libzfs C function C.zpool_get_prop , last argument 'boolean_t literal' should be B_TRUE. |
thanks @fkasumovic, just opened PR #26 |
Fixes #25, This was broken since libzfs 0.8, by the `literal` argument in the call to zpool_get_propetry function.
@fkasumovic is this hotfix going to be released for a new version? |
https://github.com/bicomsystems/go-libzfs/releases/tag/v0.3.0 |
I noticed a difference between values provided by
zfs.Dataset
properties andzfs.Pool
ones: basically, on ZPool instances, quantity resources like space allocated or space size are expressed as human-readable value, as opposed to what's happening with Dataset where I can get bytes values with ease.I tried to dig deeper on the C implementation but hadn't luck: do you plan to fill this gap of properties presentation?
JFI ZPool allows to retrieve parsable values:
The text was updated successfully, but these errors were encountered: