OpenSolaris

Printable Version Enter a New Search
Bug ID 6596228
Synopsis zfs upgrade -a doesn't always log to all pools
State 10-Fix Delivered (Fix available in build)
Category:Subcategory utility:zfs
Keywords
Responsible Engineer Eric Kustarz
Reported Against
Duplicate Of
Introduced In solaris_nevada
Commit to Fix snv_73
Fixed In snv_73
Release Fixed solaris_nevada(snv_73) , solaris_10u6(s10u6_01) (Bug ID:2156462)
Related Bugs
Submit Date 23-August-2007
Last Update Date 29-April-2008
Description 
Two pools of the same length but different names won't log 'zfs upgrade -a' to both pools:
# zpool create -f f1 c1t1d0s6
# zpool create -f f3 c1t1d0s7
# zfs create -o version=1 f1/a
# zfs create -o version=1 f3/a
# zfs upgrade -a
# zpool history
History for 'f1':
2007-08-23.00:13:03 zpool create -f f1 c1t1d0s6
2007-08-23.00:13:05 zfs create -o version=1 f1/a
2007-08-23.00:13:09 zfs upgrade -a

History for 'f3':
2007-08-23.00:13:04 zpool create -f f3 c1t1d0s7
2007-08-23.00:13:05 zfs create -o version=1 f3/a


The function same_pool() has backwards logic for its strncmp() routine.

PS: its really cool that we can use 'set version' - makes testing life much easier!
Work Around 
N/A
Comments 
N/A