HEADS UP: ZFS v28 merged to 8-STABLE

[Jason Hellenthal]

On Thu, Jun 09, 2011 at 12:59:39AM +0200, C. P. Ghost wrote:
> On Thu, Jun 9, 2011 at 12:55 AM, Marius Strobl
> <marius at alchemy.franken.de> wrote:
> > On Thu, Jun 09, 2011 at 12:46:19AM +0200, C. P. Ghost wrote:
> >> On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl
> >> <marius at alchemy.franken.de> wrote:
> >> > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote:
> >> >> Hi,
> >> >>
> >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741)
> >> >>
> >> >> New major features:
> >> >>
> >> >> - data deduplication
> >> >> - triple parity RAIDZ (RAIDZ3)
> >> >> - zfs diff
> >> >> - zpool split
> >> >> - snapshot holds
> >> >> - zpool import -F. Allows to rewind corrupted pool to earlier
> >> >> ? transaction group
> >> >> - possibility to import pool in read-only mode
> >> >>
> >> >> For updating, there is a compatibility layer so that in the update phase
> >> >> most functionality of the new zfs binaries can be used with the old
> >> >> kernel module and old zfs binaries with the new kernel module.
> >> >
> >> > Beware that the compatibility layer is known broken on big-endian
> >> > architectures, i.e. powerpc64 and sparc64.
> >>
> >> Thanks for the heads-up! I was just about to update a couple of sparc64
> >> machines here. Fortunately, the only ZFS file systems there are external
> >> file systems (no /, /usr, /var etc...), so it's gonna be painless, I suppose.
> >> But what about other layouts? Does it mean that an installkernel, reboot,
> >> and installworld won't work?
> >
> > No, using the old zfs binaries with the new kernel module triggers the
> > problem. Using the new zfs binaries with the new kernel module works
> > (at least with CURRENT) so you'd need disregard everything that is
> > documented and do what is not guaranteed to work but usually also does,
> > i.e. do installkernel, installworld and then reboot.
> 
> Ah, yes, that's what I expected. Thank you!
> 

To add to this, what may or may not help you. If you
installkernel+installworld and shutdown your pool might not umount
cleanly or system might hang. If you create a copy of all the old zfs
binaries into a seperate directory and run ldconfig -m
/path/to/directory and make sure that the zfs and zpool binaries are in
the PATH before shutdown for the scripts that run then you should be
able to do this flawlessly and have a perfect working system after you
reboot. This may require editing the zfs rcNG scripts to adjust the path
for only shutdown. If all else fails remove the /boot/zfs/zpool.cache
file after a reboot into single user mode then unload and reload the zfs
and opensolaris modules and this should get you going in the right
direction.


Good luck.

-- 

"Unity can only be manifested by the Binary. Unity itself and the idea of Unity are already two." -- Buddha

 Regards, (jhell)
 Jason Hellenthal

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 522 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20110610/a1f2cc5b/attachment.pgp