Just upgraded my work mac to Leopard. Took an hour, worked flawlessly.
Of course, the first thing I did was stick in a USB stick with holds half a zpool from my Solaris Express box at home:
planb:~ $ zpool import
pool: sticky
id: 4692054964394431575
state: FAULTED
status: The pool is formatted using an incompatible version.
action: The pool cannot be imported.
Access the pool on a system running newer
software, or recreate the pool from backup.
see: http://www.sun.com/msg/ZFS-8000-A5
config:
sticky UNAVAIL newer version
mirror DEGRADED
dsk/c6t0d0 UNAVAIL cannot open
disk3 ONLINE
planb:~ $ zpool import sticky
cannot import 'sticky': pool is formatted using a newer ZFS version
i.e. ” I know this is half of a mirror, but it’s a newer ZFS version than Apples”.
what’s new pussycat?
So I reformatted the disk on my Solaris 10 update 4 box:
vera / # rmformat
Looking for devices...
...
...
3. Volmgt Node: /vol/dev/aliases/rmdisk0
Logical Node: /dev/rdsk/c4t0d0p0
Physical Node: /pci@0,0/pci8086,4c43@1d,7/storage@7/disk@0,0
Connected Device: Kingston DataTraveler 2.0 PMAP
Device Type: Removable
vera / # zpool create sticky c4t0d0p0
This is how it looks on Solaris 10:
vera / # zpool status sticky
pool: sticky
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
sticky ONLINE 0 0 0
c4t0d0p0 ONLINE 0 0 0
errors: No known data errors
vera / # zfs list /sticky
NAME USED AVAIL REFER MOUNTPOINT
sticky 85K 1.87G 24.5K /sticky
So I copied a bit of data on, zpool exported and stuck it back in the Mac.
planb:~ $ zpool import sticky
planb:~ $ zpool status
pool: sticky
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'. Once this is done, the
pool will no longer be accessible on older software versions.
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
sticky ONLINE 0 0 0
disk3 ONLINE 0 0 0
errors: No known data errors
planb:~ $ zfs list
NAME USED AVAIL REFER MOUNTPOINT
sticky 30.8M 1.84G 30.7M /Volumes/sticky
planb:~ $ ls -l /Volumes/sticky/
total 3
dr-xr-xr-x+ 4 root sys 6 7 Nov 00:10 local
planb:~ $ touch /Volumes/sticky/bummer
touch: /Volumes/sticky/bummer: Read-only file system
Much better.
pussy galore
Now for the crazy conspicacy theory bit:
planb:~ $ zpool get all sticky cannot get property 'name': pool must be upgraded to support pool properties cannot get property 'bootfs': pool must be upgraded to support pool properties cannot get property 'bootfs': pool must be upgraded to support pool properties
i.e. “this zpool format doesn’t support bootable volumes. but I do.”
Take a look at http://www.opensolaris.org/os/community/zfs/version/6/ ZFS Pool Version 6 This page describes the feature available with version 6 of the ZFS on-disk format. This version includes support for the following feature: * ‘bootfs’ pool property This feature is available in: * Solaris Nevada Build 62 The related bugs for version 6 changes are as follows: * 4929890 ZFS Boot support for the x86 platform * 6479807 pools need properties
You can see a short summary of the zpool versions Leopard supports at the command line. This is what my system shows with the ZFS 1.1 read/write kernel extension from the Apple Dev site:
Not sure what “OSX directory type” means, but it isn’t listed on the ZFS version page. It looks like Sun is already up to zpool version 9, so hopefully we’ll see a Apple ZFS 1.2 kernel extension posted on the ADC in the near future.
@Stan : my guess is that ‘OSX directory type’ is going to be related to the directory hard links required to do Time Machine. But I just signed up to the Developer Program (so I can get read/write) and that means I have to keep quiet now