[Not Accepted] ZFS version bug - upstream

Problem/Justification

The manual page does not match the actual command’s abilities. This is likely upstream issue. But, it’s a simple fix…

Impact

Annoying to have multiple documented methods, in the manual pages for both zfs & zpool command fail:

SUBCOMMANDS
     All subcommands that modify state are logged persistently to the pool in their original form.

     zfs -?
       Displays a help message.

     zfs -V, --version
SUBCOMMANDS
     All subcommands that modify state are logged persistently to the pool in their original form.

     The zpool command provides subcommands to create and destroy storage pools, add capacity to storage pools,
     and provide information about the storage pools.  The following subcommands are supported:

     zpool -?
             Displays a help message.

     zpool -V, --version

User Story

I was trying to get the version of OpenZFS using the normal command line method.

root@truenas[~]# zfs -V
invalid option 'V'
usage: zfs command args ...
where 'command' is one of the following:

	version [-j]
...
root@truenas[~]# zfs --version
invalid option ''
usage: zfs command args ...
where 'command' is one of the following:

	version [-j]
...
root@truenas[~]# zpool -V
invalid option 'V'
usage: zpool command args ...
where 'command' is one of the following:

	version [-j]
...
root@truenas[~]# zpool --version
invalid option ''
usage: zpool command args ...
where 'command' is one of the following:

	version [-j]
...

To be clear, I was able to get the OpenZFS version using the `version` sub-command... but that did not exist previously so I did not know about it. Plus, `zfs -V` is much shorter typing, so that is what I memorized :-). if I get around TUIT, I might submit the request to fix myself.

This seems more like a bug report than a feature request. Also, it’s redundant since the upcoming version of TrueNAS Scale has updated tools and e.g. zfs -V works just fine.

2 Likes

You are probably right, bug verses feature request.

Weird that it’s broke for a specific version of OpenZFS. But, it was a bit of a frankenZFS because it included the RAID-Zx Expansion feature before the official OpenZFS 2.3.0 version.