On 03/05/09 11:33, Richard Morris - Sun Microsystems - Burlington United
States wrote:
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.
This evaluation is not completely correct. The zpool command does allow the
on-disk version of the root dataset to be set to current using the -O
option:
# zpool create -O version=current pool /tmp/pool
# zfs get version pool
NAME PROPERTY VALUE SOURCE
pool version 3 -
But the zpool command does not also allow the on-disk version of the pool
to be set to current:
# zpool create -o version=current pool /tmp/pool
cannot create 'pool': bad numeric value 'current'
-- Rich
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
