On 03/04/09 15:24, Dennis Clarke wrote:
Not too sure what this option needs as a value but the man page suggests that the keywork "current" should work.... cannot create 'fibre00': bad numeric value 'current' The keyword current is not numeric and causes an issue. The zpool(1M) manpage is not clear on this and, I really don't know if quotes would help here. In zpool(1M) section Properties we see : version=version The current on-disk version of the pool. This can be increased, but never decreased. The preferred method of updating pools is with the "zpool upgrade" command, though this property can be used when a specific version is needed for backwards compatibility. This property can be any number between 1 and the current version reported by "zpool upgrade -v". The special value "current" is an alias for the latest supported version.
That last sentence is incorrect. The zpool command does not support "current" as an alias for the last supported version. However the zfs command does: # zpool create -o version=current pool /tmppool cannot create 'pool': bad numeric value 'current' # zfs create -o version=current pool2/fs # zfs get version pool2/fs NAME PROPERTY VALUE SOURCE pool2/fs version 3 - Filed CR 6813635 to correct this info in the zpool(1M) man page. Filed RFE 6813645 to add support for version=current to the zpool command. Once that RFE is implemented, the last sentence above can be added back to the zpool(1M) man page. But until that RFE is implemented, perhaps zpool create -n version=current should report an error. -- Rich
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
