I assume the zpool is on a second disk(s). If so, zpool export pool, do the
installation of _95 and zpool import pool. Your data will be safe even if you
don't export the pool, but, I'm paranoid. I used to do it that way before I
decided to try Live Upgrade.
--ron
This message posted from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Halstead wrote:
| I assume the zpool is on a second disk(s). If so, zpool export pool,
do the installation of _95 and zpool import pool. Your data will be safe
even if you don't export the pool, but, I'm paranoid. I used to do it
that way before I
Zpools are self contained, so as stated before its safe. In upgrades like this
I often will actually pull or disconnect the zpool disks just for paranoia sake.
As for the config of the existing machine, keeping a copy of /etc is never a
bad idea. I typically will rsync a copy of it out
Ben Rockwood wrote:
Zpools are self contained, so as stated before its safe. In upgrades like
this I often will actually pull or disconnect the zpool disks just for
paranoia sake.
As for the config of the existing machine, keeping a copy of /etc is never a
bad idea. I typically will
Ben Rockwood writes:
Upgrades get even easier if you put filesystems like /opt or /usr/local on
the zpool. Post-install just mount /opt and /usr/local from the zpool (zfs
set mountpoint=/usr/local pool/local zfs mount -a). I frequently upgrade
my Nevada boxes (read: reinstall) and
Ian Collins wrote:
Ben Rockwood writes:
Upgrades get even easier if you put filesystems like /opt or
/usr/local on the zpool. Post-install just mount /opt and /usr/local
from the zpool (zfs set mountpoint=/usr/local pool/local zfs mount
-a). I frequently upgrade my Nevada boxes (read:
Ian Collins wrote:
Ben Rockwood writes:
Upgrades get even easier if you put filesystems like /opt or
/usr/local on the zpool. Post-install just mount /opt and /usr/local
from the zpool (zfs set mountpoint=/usr/local pool/local zfs mount
-a). I frequently upgrade my Nevada boxes (read:
