On 04/21/09 13:12, bob netherton wrote:
since I am trying to keep my pools at a version that different updates
can handle, I personally am glad it did not get rev'ed. I did get into
trouble recently that SX-CE 112 created a file system on an old pool
with a version newer than Solaris 10 likes :(
-o is your best friend ;-) I can now get rid of all of those
pre-allocated filesystems
that I used for just this purpose. Don't know where all of the corner
cases are, but
this appears to be a workaround. Just keep a table of the pool and
filesystem versions
for each release handy.
# zpool create -o version=10 newpool c0d0s4
I did this on nv112 and ..... drum roll please ...... it can be
imported on Solaris 10.
Same thing for ZFS.
# zfs create -o version=1 rpool/legacy-file-system
Also created on nv112 and also .... wait for it ....... mountable and
totally
usable on Solaris 10 10/08.
It's a beautiful thing.
Thanks, Bob. I figured that much, just got surprise (and only recently),
and when I switched back to S10 8/07 to diagnose a customer problem, I
got error messages!
Fortunately it was still able to boot, and mount!
# zfs get version mypool/zones-snv112-090414/master
NAME PROPERTY VALUE
SOURCE
mypool/zones-snv112-090414/master version 2
-
# zfs get version mypool
NAME PROPERTY VALUE SOURCE
mypool version 1 -
Note that the file systems are being created by zoneadm. However, since
I created the mypool/zones-snv112-090414 filesystem by hand (on 112), I
will have to verify that a clone of it will keep the version as the origin.
Steffen
Bob
_______________________________________________
zfs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
