Skip to content

My first ZFS to ZFS live upgrade

June 10, 2008

My first live upgrade from ZFS to ZFS was as boring as you could wish for.


# luactivate zfs91 System has findroot enabled GRUB Generating boot-sign, partition and slice information for PBE <zfs90>  Generating boot-sign for ABE <zfs91> Generating partition and slice information for ABE <zfs91> Boot menu exists. Generating direct boot menu entries for PBE. Generating xVM menu entries for PBE. Generating direct boot menu entries for ABE. Generating xVM menu entries for ABE. No more bootadm entries. Deletion of bootadm entries is complete. GRUB menu default setting is unaffected Done eliding bootadm entries.  **********************************************************************  The target boot environment has been activated. It will be used when you  reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You  MUST USE either the init or the shutdown command when you reboot. If you  do not use either init or shutdown, the system will not boot using the  target BE.  **********************************************************************  In case of a failure while booting to the target BE, the following process  needs to be followed to fallback to the currently working boot environment:  1. Boot from Solaris failsafe or boot in single user mode from the Solaris  Install CD or Network.  2. Mount the Parent boot environment root slice to some directory (like  /mnt). You can use the following command to mount:       mount -Fzfs /dev/dsk/c0d0s0 /mnt  3. Run <luactivate> utility with out any arguments from the Parent boot  environment root slice, as shown below:       /mnt/sbin/luactivate  4. luactivate, activates the previous working boot environment and  indicates the result.  5. Exit Single User mode and reboot the machine.  **********************************************************************  Modifying boot archive service Activation of boot environment <zfs91> successful. #  init 6 #

See all very dull. After it rebooted:

: pearson FSS 8 $; ssh sigma-wired Last login: Tue Jun 10 12:51:59 2008 from pearson.thegerh Sun Microsystems Inc.   SunOS 5.11      snv_91  January 2008 : sigma TS 1 $; su – kroot Password:  # lustatus Boot Environment           Is       Active Active    Can    Copy       Name                       Complete Now    On Reboot Delete Status     ————————– ——– —— ——— —— ———- ufs90                      yes      no     no        yes    –          zfs90                      yes      no     no        yes    –          zfs91                      yes      yes    yes       no     –          #

Although I’m not sure I like this:

# zfs list -r tank/ROOT NAME                                  USED  AVAIL  REFER  MOUNTPOINT tank/ROOT                            7.90G  8.81G    18K  /export/ROOT tank/ROOT@zfs90                        17K      –    18K  – tank/ROOT/zfs90                      4.94M  8.81G  5.37G  /.alt.tmp.b-uK.mnt/ tank/ROOT/zfs91-notyet               7.89G  8.81G  5.39G  / tank/ROOT/zfs91-notyet@zfs90         70.5M      –  5.37G  – tank/ROOT/zfs91-notyet@zfs91-notyet  63.7M      –  5.37G  – # 

I have got used to renaming my exising BE to be nvXX-notyet and then upgrading that. So with ZFS I created a BE called zfs91-notyet upgraded that and then renamed it back. It seems that the renaming of a BE does not rename the underlying filesystems. Easy to work around but is it a bug?

Advertisements

From → Solaris

3 Comments
  1. Mark J Musante permalink

    File an RFE, please. It’s been an interesting few months getting the live upgrade code to understand zfs, and there are still several things we need to clean up. Renaming datasets during lurename should be one of them.

  2. I just filed:
    CR 6713231 Created P3 solaris_inst/live-upgrade lurename of ZFS BE should rename the zfs datasets
    I think this is a bug as it prevents you creating BEs with the old name.

  3. There is a related bug in the new OpenSolaris 2008.05 beadm command where you can’t rename the running be because the filesystem is mounted.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: