Live upgrade only for zfs root?

Only live upgrade for zfs root on 5/09? Is this true? I have tried to do live upgrades previously and have had no luck. Particularly on my old blade1000 with an 18gb drive.

Reading over this post I see it is a little unclear. I am trying to upgrade a u6 installation that has a zfs root to u7.

Similar Messages

Solaris 10 5/08 live upgrade only for customers with serviceplan ?

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Live upgrade fails due to missing /usr/bin/7za
Which seems to be installed by adding patch 137322-01 on x86 according to release notes http://docs.sun.com/app/docs/doc/820-4078/installbugs-114?l=en&a=view
But this patch (may also be the case for Sparc patch) are only available for customers with a valid serviceplan.
Does this mean that from now on its required to purchase a serviceplan if you would run Solaris 10 and use the normal procedures for system upgrades ?
A bit disappointing ...
Regards
/Flemming

Solaris 10 update 9 - live upgrade issues with ZFS

Hi
After doing a live upgrade from Solaris 10 update 8 to Solaris 10 update 9 the alternate boot environment I created is no longer bootable.
I have completed all the pre-upgrade steps like:
- Installing the latest version of live upgrade from the update 9 ISO.
- Create and test the new boot environment.
- Create a sysidcfg file used by the live upgrade that has auto_reg=disable in it.
There is also no errors while creating the boot environment or even when activating it.
Here is the error I get:
SunOS Release 5.10 Version Generic_14489-06 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
NOTICE: zfs_parse_bootfs: error 22
Cannot mount root on altroot/37 fstype zfs
*panic[cpu0]/thread=fffffffffbc28040: vfs mountroot: cannot mount root*
ffffffffffbc4a8d0 genunix:main+107 ()
Skipping system dump - no dump device configured
Does anyone know how I can fix this?
Edited by: user12099270 on 02-Feb-2011 04:49

Found the culprit... *142910-17*... breaks it
System has findroot enabled GRUB
Updating GRUB menu default setting
GRUB menu default setting is unaffected
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <s10x_u8wos_08a> as <mount-point>//boot/grub/menu.lst.prev.
File </etc/lu/GRUB_backup_menu> propagation successful
Successfully deleted entry from GRUB menu
Validating the contents of the media </admin/x86/Patches/10_x86_Recommended/patches>.
The media contains 204 software patches that can be added.
Mounting the BE <s10x_u8wos_08a_Jan2011>.
Adding patches to the BE <s10x_u8wos_08a_Jan2011>.
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWio-tools from directory SUNWio-tools in patch 142910-17 is not installed on the system. Changes for package SUNWio-tools will not be applied to the system.
Package SUNWzoneu from directory SUNWzoneu in patch 142910-17 is not installed on the system. Changes for package SUNWzoneu will not be applied to the system.
Package SUNWpsm-ipp from directory SUNWpsm-ipp in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-ipp will not be applied to the system.
Package SUNWsshdu from directory SUNWsshdu in patch 142910-17 is not installed on the system. Changes for package SUNWsshdu will not be applied to the system.
Package SUNWsacom from directory SUNWsacom in patch 142910-17 is not installed on the system. Changes for package SUNWsacom will not be applied to the system.
Package SUNWmdbr from directory SUNWmdbr in patch 142910-17 is not installed on the system. Changes for package SUNWmdbr will not be applied to the system.
Package SUNWopenssl-commands from directory SUNWopenssl-commands in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-commands will not be applied to the system.
Package SUNWsshdr from directory SUNWsshdr in patch 142910-17 is not installed on the system. Changes for package SUNWsshdr will not be applied to the system.
Package SUNWsshcu from directory SUNWsshcu in patch 142910-17 is not installed on the system. Changes for package SUNWsshcu will not be applied to the system.
Package SUNWsshu from directory SUNWsshu in patch 142910-17 is not installed on the system. Changes for package SUNWsshu will not be applied to the system.
Package SUNWgrubS from directory SUNWgrubS in patch 142910-17 is not installed on the system. Changes for package SUNWgrubS will not be applied to the system.
Package SUNWzoner from directory SUNWzoner in patch 142910-17 is not installed on the system. Changes for package SUNWzoner will not be applied to the system.
Package SUNWmdb from directory SUNWmdb in patch 142910-17 is not installed on the system. Changes for package SUNWmdb will not be applied to the system.
Package SUNWpool from directory SUNWpool in patch 142910-17 is not installed on the system. Changes for package SUNWpool will not be applied to the system.
Package SUNWudfr from directory SUNWudfr in patch 142910-17 is not installed on the system. Changes for package SUNWudfr will not be applied to the system.
Package SUNWxcu4 from directory SUNWxcu4 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu4 will not be applied to the system.
Package SUNWarc from directory SUNWarc in patch 142910-17 is not installed on the system. Changes for package SUNWarc will not be applied to the system.
Package SUNWtftp from directory SUNWtftp in patch 142910-17 is not installed on the system. Changes for package SUNWtftp will not be applied to the system.
Package SUNWaccu from directory SUNWaccu in patch 142910-17 is not installed on the system. Changes for package SUNWaccu will not be applied to the system.
Package SUNWppm from directory SUNWppm in patch 142910-17 is not installed on the system. Changes for package SUNWppm will not be applied to the system.
Package SUNWtoo from directory SUNWtoo in patch 142910-17 is not installed on the system. Changes for package SUNWtoo will not be applied to the system.
Package SUNWcpc from directory SUNWcpc.i in patch 142910-17 is not installed on the system. Changes for package SUNWcpc will not be applied to the system.
Package SUNWftdur from directory SUNWftdur in patch 142910-17 is not installed on the system. Changes for package SUNWftdur will not be applied to the system.
Package SUNWypr from directory SUNWypr in patch 142910-17 is not installed on the system. Changes for package SUNWypr will not be applied to the system.
Package SUNWlxr from directory SUNWlxr in patch 142910-17 is not installed on the system. Changes for package SUNWlxr will not be applied to the system.
Package SUNWdcar from directory SUNWdcar in patch 142910-17 is not installed on the system. Changes for package SUNWdcar will not be applied to the system.
Package SUNWnfssu from directory SUNWnfssu in patch 142910-17 is not installed on the system. Changes for package SUNWnfssu will not be applied to the system.
Package SUNWpcmem from directory SUNWpcmem in patch 142910-17 is not installed on the system. Changes for package SUNWpcmem will not be applied to the system.
Package SUNWlxu from directory SUNWlxu in patch 142910-17 is not installed on the system. Changes for package SUNWlxu will not be applied to the system.
Package SUNWxcu6 from directory SUNWxcu6 in patch 142910-17 is not installed on the system. Changes for package SUNWxcu6 will not be applied to the system.
Package SUNWpcmci from directory SUNWpcmci in patch 142910-17 is not installed on the system. Changes for package SUNWpcmci will not be applied to the system.
Package SUNWarcr from directory SUNWarcr in patch 142910-17 is not installed on the system. Changes for package SUNWarcr will not be applied to the system.
Package SUNWscpu from directory SUNWscpu in patch 142910-17 is not installed on the system. Changes for package SUNWscpu will not be applied to the system.
Package SUNWcpcu from directory SUNWcpcu in patch 142910-17 is not installed on the system. Changes for package SUNWcpcu will not be applied to the system.
Package SUNWopenssl-include from directory SUNWopenssl-include in patch 142910-17 is not installed on the system. Changes for package SUNWopenssl-include will not be applied to the system.
Package SUNWdtrp from directory SUNWdtrp in patch 142910-17 is not installed on the system. Changes for package SUNWdtrp will not be applied to the system.
Package SUNWhermon from directory SUNWhermon in patch 142910-17 is not installed on the system. Changes for package SUNWhermon will not be applied to the system.
Package SUNWpsm-lpd from directory SUNWpsm-lpd in patch 142910-17 is not installed on the system. Changes for package SUNWpsm-lpd will not be applied to the system.
Package SUNWdtrc from directory SUNWdtrc in patch 142910-17 is not installed on the system. Changes for package SUNWdtrc will not be applied to the system.
Package SUNWhea from directory SUNWhea in patch 142910-17 is not installed on the system. Changes for package SUNWhea will not be applied to the system.
Package SUNW1394 from directory SUNW1394 in patch 142910-17 is not installed on the system. Changes for package SUNW1394 will not be applied to the system.
Package SUNWrds from directory SUNWrds in patch 142910-17 is not installed on the system. Changes for package SUNWrds will not be applied to the system.
Package SUNWnfsskr from directory SUNWnfsskr in patch 142910-17 is not installed on the system. Changes for package SUNWnfsskr will not be applied to the system.
Package SUNWudf from directory SUNWudf in patch 142910-17 is not installed on the system. Changes for package SUNWudf will not be applied to the system.
Package SUNWixgb from directory SUNWixgb in patch 142910-17 is not installed on the system. Changes for package SUNWixgb will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
142910-17
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 142910-17 has been successfully installed.
See /a/var/sadm/patch/142910-17/log for details
Executing postpatch script...
Creating GRUB menu in /a
Installing grub on /dev/rdsk/c2t0d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 273 sectors starting at 50 (abs 16115)
Patch packages installed:
BRCMbnx
SUNWaac
SUNWahci
SUNWamd8111s
SUNWcakr
SUNWckr
SUNWcry
SUNWcryr
SUNWcsd
SUNWcsl
SUNWcslr
SUNWcsr
SUNWcsu
SUNWesu
SUNWfmd
SUNWfmdr
SUNWgrub
SUNWhxge
SUNWib
SUNWigb
SUNWintgige
SUNWipoib
SUNWixgbe
SUNWmdr
SUNWmegasas
SUNWmptsas
SUNWmrsas
SUNWmv88sx
SUNWnfsckr
SUNWnfscr
SUNWnfscu
SUNWnge
SUNWnisu
SUNWntxn
SUNWnv-sata
SUNWnxge
SUNWopenssl-libraries
SUNWos86r
SUNWpapi
SUNWpcu
SUNWpiclu
SUNWpsdcr
SUNWpsdir
SUNWpsu
SUNWrge
SUNWrpcib
SUNWrsgk
SUNWses
SUNWsmapi
SUNWsndmr
SUNWsndmu
SUNWtavor
SUNWudapltu
SUNWusb
SUNWxge
SUNWxvmpv
SUNWzfskr
SUNWzfsr
SUNWzfsu
PBE GRUB has no capability information.
PBE GRUB has no versioning information.
ABE GRUB is newer than PBE GRUB. Updating GRUB.
GRUB update was successfull.
Unmounting the BE <s10x_u8wos_08a_Jan2011>.
The patch add to the BE <s10x_u8wos_08a_Jan2011> completed.
Still need to know how to resolve it though...

Why OS 5 upgrade only for BIS subscribers?

I have blackberry curve 8520. OS ver 4.6.something
I want to know why the OS 5 upgrade is only for BIS subscribers and not common blackberry users?
I mean we also paid the price for the phone and we also want most out of the bb. If blackberry considers the BIS subscribers the only customers then why sell the phones to others as well.
If blackberry want to decrease the number of bb admirers and users, then its a good step to limit the OS upgrade to only BIS users, otherwise whats the point of limiting the update to only BIS?
Dont they want the blackberries to look and work cool, at least compared to other cellphone giants.
Solved!
Go to Solution.

hejalaci wrote:
I do not agree,
1. I should not have to pay for newer versions of my firmware, paying them to fix what they messed up in the first place, i did not have phone until now that charged for something like that(even apple gives it away freely).
2.BIS is very expensive i WILL NOT pay 9 euro+VAT for 5 MB transfer. At these prices they might as well steal your money out of your pockets.
Wow. Where to start on this one.
First off, you are not paying for a newer version of the device software. You must pay for BIS to utilize all the features that your Blackberry has to offer, such as having your e-mail pushed to your phone, having the entire internet at your fingertips whenever you want, wherever you are. You are WASTING your Blackberry by not having BIS or BES. I'd be willing to bet that 99.9999% of Blackberry owners pay for BIS or have BES, and the other 0.0001% are the idiots who buy a blackberry to "look cool". That is not what these devices are made for, or marketed as. If you want a "cool" phone, go get a Samsung touch-screen, or an iphone.

Smpatch add -b fails for ZFS root

This is Solaris-10U6, x86, patched to current patchlevels as of this afternoon:
# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
be20081218                 yes      no     no        yes    -
be20081229                 yes      yes    yes       no     -
# smpatch analyze 2>&1 | tee /var/tmp/,patchlist
122912-14 SunOS 5.10_x86: Apache 1.3 Patch
# lucreate -n testbe
Checking GRUB menu...
System has findroot enabled GRUB
Analyzing system configuration.
Comparing source boot environment <be20081229> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <testbe>.
Source boot environment is <be20081229>.
Creating boot environment <testbe>.
Cloning file systems from boot environment <be20081229> to create boot environment <testbe>.
Creating snapshot for <rpool/ROOT/be20081229> on <rpool/ROOT/be20081229@testbe>.Creating clone for <rpool/ROOT/be20081229@testbe> on <rpool/ROOT/testbe>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/testbe>.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <be20081218> as <mount-point>//boot/grub/menu.lst.prev.
Saving existing file </boot/grub/menu.lst> in top level dataset for BE <testbe> as <mount-point>//boot/grub/menu.lst.prev.
File </boot/grub/menu.lst> propagation successful
Copied GRUB menu from PBE to ABE
No entry for BE <testbe> in GRUB menu
Population of boot environment <testbe> successful.
Creation of boot environment <testbe> successful.
# smpatch download -x idlist=/var/tmp/,patchlist
122912-14 has been validated.
# smpatch add -b testbe -x idlist=/var/tmp/,patchlist
Ckecking the currently running boot enviornment ...
Currently running boot enviornment name is [be20081229].
Checking the destination boot environment [testbe] ...
Copying the cuurently running BE into inactive BE [testbe] ...
This grogess will take you a long time, please wait a moment.)
ERROR: File systems on ABE <testbe> have insufficient space for repopulation from boot environment <be20081229>. It is recommended to delete this BE and create a fresh BE.
/usr/sbin/lumake: lumake into testbe failed
#

I think the problem is generated by the following line in /usr/sbin/lumake:
$LUBIN/lucomp_size -p $PBE_NAME -i ${ICF} -O $INODE_ICF -n $ABE_NAMEThis command calls /usr/lib/lu/lucomp_size and it is this which is returning a 1, and ultimately causes the "insufficient space" error.
To find out what is going wrong when lumake checks the size, please enable the printing of commands and arguments and run the command again:
# script /var/tmp/smpatch.out
# set -x
# smpatch add -b testbe -x idlist=/var/tmp/,patchlist
# set +x
# exitOnce this has completed, please look through the /var/tmp/smpatch.out and then run the corresponding lucomp_size command and check the output and exit code:
# /usr/lib/lu/lucomp_size <args>
# echo $?If you are absolutely certain that there is enough space and just want to make this work now, you could remove the following lines from lumake:
$LUBIN/lucomp_size -p $PBE_NAME -i ${ICF} -O $INODE_ICF -n $ABE_NAME
if [ "$?" -ne "0" ] ; then
    # Size is not sufficient
    ${LUPRINTF} -Eelp2 "`gettext 'File systems on ABE <%s> have insufficient \
space for repopulation from boot environment <%s>. It is recommended to \
delete this BE and create a fresh BE.'`" "${ABE_NAME}" "${PBE_NAME}"
    err_exit_script 1
fiI would recommend that you open a support call so that the issue can be progressed more quickly.

Flarecreate for zfs root dataset and ignore multiple dataset

Hi All,
I want to write a script to create flar images on multiple servers. In non zfs filesystem I am using -X option to refer a file to exclude mounts on different servers.
but on ZFS -X option is not working. I want multiple mounts to be ignore on ZFS base system during flarecreate.
I can use -D option to ignore the datasets on the server but it is not serving my purpose as i am maintaining a common file to ignore the mounts on all different servers.
Please help me in this

Renaming the root pool is not recommended.

Adobe live pdf only for AIR ?

Hello,
How can i use the Adobe live PDF generator, i've seen a few exmples ... it requires the AIR for the examples i've seen, but does it support flex i.e., pdf over browser? if so, is there a good example code i could find ? thanks for the help.

I don't know about LiveCycle PDF Generator but the LiveCycle Data Services ES server has a PDF generation feature that works with the Flash Player, not just with AIR.
You can check my entries about LCDS and PDF in the Flex Cookbook Beta website.

Upgrade only for previous $20 update or basic iPod touch?

For anyone that has seen the keynote, will the 2.0 upgrade be an upgrade for first Software Update or for anyone that didn't buy the Software Update several months ago? Will I be forced to buy the first one (the $20) to get the second ($10) one?
Just throwing that out there in case anyone has found the relevant information.

And a wild guess will get you the Apps will be available in the App Store.
Guessing is fun.

Dolby Digital Live upgrade availability for SB Audigy us

Hello everyone,
We understand SB Audigy users are eagerly anticipating the Dolby Digital Li've upgrade availability. We are still working on the development. Unfortunately, the work requires more time than anticipated earlier due to the difference in the Audigy product architecture vs the X-Fi product architecture as well as testing required to ensure stable and correct functionality. We estimate Dolby Digital upgrade for Audigy to be available in late Dec 2008. We apologize for the delay and are trying our best to release earlier if possible.
Thank you,
The Sound Blaster Team

Dear Sound Blaster Audigy users,
Dolby Digital Li've For Audigy users!
We are pleased to announce that the http://buy.soundblaster.com at US$4.72.
Please check out the website for more information on how to make the upgrade for your card.
Thank you,
The Sound Blaster Team.
Message Edited by KokChoy-CL on <span class='local-date'> 03-26-2009<span class='local-time'> 05:09 [email protected]

Best practices for ZFS file systems when using live upgrade?

I would like feedback on how to layout the ZFS file system to deal with files that are constantly changing during the Live Upgrade process. For the rest of this post, lets assume I am building a very active FreeRadius server with log files that are constantly updating and must be preserved in any boot environment during the LU process.
Here is the ZFS layout I have come up with (swap, home, etc omitted):
NAME                                USED AVAIL REFER MOUNTPOINT
rpool                              11.0G 52.0G    94K /rpool
rpool/ROOT                         4.80G 52.0G    18K legacy
rpool/ROOT/boot1                   4.80G 52.0G 4.28G /
rpool/ROOT/boot1/zones-root         534M 52.0G    20K /zones-root
rpool/ROOT/boot1/zones-root/zone1   534M 52.0G   534M /zones-root/zone1
rpool/zone-data                      37K 52.0G    19K /zones-data
rpool/zone-data/zone1-runtime        18K 52.0G    18K /zones-data/zone1-runtimeThere are 2 key components here:
1) The ROOT file system - This stores the / file systems of the local and global zones.
2) The zone-data file system - This stores the data that will be changing within the local zones.
Here is the configuration for the zone itself:
<zone name="zone1" zonepath="/zones-root/zone1" autoboot="true" bootargs="-m verbose">
<inherited-pkg-dir directory="/lib"/>
<inherited-pkg-dir directory="/platform"/>
<inherited-pkg-dir directory="/sbin"/>
<inherited-pkg-dir directory="/usr"/>
<filesystem special="/zones-data/zone1-runtime" directory="/runtime" type="lofs"/>
<network address="192.168.0.1" physical="e1000g0"/>
</zone>The key components here are:
1) The local zone / is shared in the same file system as global zone /
2) The /runtime file system in the local zone is stored outside of the global rpool/ROOT file system in order to maintain data that changes across the live upgrade boot environments.
The system (local and global zone) will operate like this:
The global zone is used to manage zones only.
Application software that has constantly changing data will be installed in the /runtime directory within the local zone. For example, FreeRadius will be installed in: /runtime/freeradius
During a live upgrade the / file system in both the local and global zones will get updated, while /runtime is mounted untouched in whatever boot environment that is loaded.
Does this make sense? Is there a better way to accomplish what I am looking for? This this setup going to cause any problems?
What I would really like is to not have to worry about any of this and just install the application software where ever the software supplier sets it defaults to. It would be great if this system somehow magically knows to leave my changing data alone across boot environments.
Thanks in advance for your feedback!
--Jason

Hello "jemurray".
Have you read this document? (page 198)
http://docs.sun.com/app/docs/doc/820-7013?l=en
Then the solution is:
01.- Create an alternate boot enviroment
a.- In a new rpool
b.- In the same rpool
02.- Upgrade this new enviroment
03.- Then I've seen that you have the "radious-zone" in a sparse zone (it's that right??) so, when you update the alternate boot enviroment you will (at the same time) upgrading the "radious-zone".
This maybe sound easy but you should be carefull, please try this in a development enviroment
Good luck

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

ZFS root and Live upgrade

Is it possible to create /var as its own ZFS dataset when using liveupgrade? With ufs, there's the -m option to lucreate. It seems like any liveupgrade to a ZFS root results in just the root, dump, and swap datasets for the boot environment.
merill

Hey man.
I bad my head against the wall with the same question :-)
One thing that might help you out anyway is that i found a solution on how to move ufs filesystems to the new ZFS pool.
Let's say you have a ufs fs with let's say application server and stuff on /app which is on c1t0d0s6.
When you create the new ZFS based BE the /app is shared.
In order to move it to the new BE, all you need to do is to comment the lines in /etc/vfstab you want to be moved.
then run lucreate to create the ZFS BE.
After that, create a new dataset for /app, just give it a different mountpoint.
Copy all your stuff.
rename the original /app
and set the dataset's mountpoint
this is it, all your stuff are now on ZFS.
Hope it will be usefull,

RFE: smpatch for Live Upgrade boot environments

We use smpatch extensively, along with a local patch server, to keep our Solaris servers
and workstations up to date on patches. I'm relatively satisfied with this facility.
I'd like to use smpatch to apply patches to a Live Upgrade boot environment, but it
doesn't offer that option. All I really need to do is to point it at an alternate root to do
the analysis and patch download. Live Upgrade already has the ability to apply patches
from a local directory. I've had to turn to the competition, pca, to do the analysis and
download.
Please request that this ability be added to smpatch.

Unfortunately man pages are not usually updated after an initial release. However there is a change request 6481979 to add it to the man pages. The option is now present in the smpatch help when no parameters are provided to the command only as "-b boot-env". As an example;
$ smpatch add -b altboot -i 111111-11
The relevent change requests were 6366823 for Update Connection and 4974240 historically for smpatch. As realisation detection used in an analysis may depend on active software or drivers to extract data this cannot be statically extracted from a system image so a correct analysis cannot be done which appears to be why only add, remove and update were given the boot environment option.

Looking for information on best practices using Live Upgrade to patch LDOMs

This is in Solaris 10. Relatively new to the style of patching... I have a T5240 with 4 LDOMS. A control LDOM and three clients. I have some fundamental questions I'd like help with..
Namely:
#1. The Client LDOMS have zones running in them. Do I need to init 0 the zone or can I just +zoneadm zone halt+ them regardless of state? I.E. if it's running a database will halting the zone essentially snapshot it or will it attempt to shut it down. Is this even a nessessary step.
#2. What is the reccommended reboot order for the LDOMs? do I need to init 0 the client ldoms and the reboot the control ldom or can I leave the client LDOM's running and just reboot the control and then reboot the clients after the control comes up?
#3. Oracle. it's running in several of the zones on the client LDOM's what considerations need to be made for this?
I am sure other things will come up during the conversation but I have been looking for an hour on Oracle's site for this and the only thing I can find is old Sun Docs with broken links.
Thanks for any help you can provide,
pipelineadmin+*

Before you use live upgrade, or any other patching technique for Solaris, please be sure to read http://docs.oracle.com/cd/E23823_01/html/E23801/index.html which includes information on upgrading systems with non-global zones. Also, go to support.oracle.com and read Oracle Solaris Live Upgrade Information Center [ID 1364140.1]. These really are MANDATORY READING.
For the individual questions:
#1. During the actual maintenance you don't have to do anything to the zone - just operate it as normal. That's the purpose of the "live" in "live upgrade" - you're applying patches on a live, running system under normal operations. When you are finisihed with that process you can then reboot into the new "boot environment". This will become more clear after reading the above documents. Do as you normally would do before taking a planned outage: shut the databases down using the database commands for a graceful shutdown. A zone halt will abruptly stop the zone and is not a good idea for a database. Alternatively, if you can take application outages, you could (smoothly) shutdown the applications and then their domains, detach the zones (zoneadm detach) and then do a live upgrade. Some people like that because it makes things faster. After the live upgrade you would reboot and then zoneadm attach the zones again. The fact that the Solaris instance is running within a logical domain really is mostly besides the point with respect to this process.
As you can see, there are a LOT of options and choices here, so it's important to read the doc. I ***strongly*** recommend you practice on a test domain so you can get used to the procedure. That's one of the benefits of virtualization: you can easily set up test environments so you cn test out procedures. Do it! :-)
#2 First, note that you can update the domains individually at separate times, just as if they were separate physical machines. So, you could update the guest domains one week (all at once or one at a time), reboot them into the new Solaris 10 software level, and then a few weeks later (or whenever) update the control domain.
If you had set up your T5240 in a split-bus configuration with an alternate I/O domain providing virtual I/O for the guests, you would be able to upgrade the extra I/O domain and the control domain one at a time in a rolling upgrade - without ever having to reboot the guests. That's really powerful for providing continuous availability. Since you haven't done that, the answer is that at the point you reboot the control domain the guests will lose their I/O. They don't crash, and technically you could just have them continue until the control domain comes back up at which time the I/O devices reappear. For an important application like a database I wouldn't recommend that. Instead: shutdown the guests. then reboot the control domain, then bring the guest domains back up.
3. The fact that Oracle database is running in zones inside those domains really isn't an issue. You should study the zones administration guide to understand the operational aspects of running with zones, and make sure that the patches are compatible with the version of Oracle.
I STRONGLY recommend reading the documents mentioned at top, and setting up a test domain to practice on. It shouldn't be hard for you to find documentation. Go to www.oracle.com and hover your mouse over "Oracle Technology Network". You'll see a window with a menu of choices, one of which is "Documentation" - click on that. From there, click on System Software, and it takes you right to the links for Solaris 10 and 11.

Volume as install disk for Guest Domain and Live Upgrade

Hi Folks,
I am new to LDOMs and have some questions - any pointers, examples would be much appreciated:
(1) With support for volumes to be used as whole disks added in LDOM release 1.0.3, can we export a whole LUN under either VERITAS DMP or mpxio control to guest domain and install Solaris on it ? Any gotchas or special config required to do this ?
(2) Can Solaris Live Upgrade be used with Guest LDOMs ? or is this ability limited to Control Domains ?
Thanks

The answer to your #1 question is YES.
Here's my mpxio enabled device.
non-STMS device name STMS device name
/dev/rdsk/c2t50060E8010029B33d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
/dev/rdsk/c3t50060E8010029B37d16 /dev/rdsk/c4t4849544143484920373730313036373530303136d0
create the virtual disk using slice 2
ldm add-vdsdev /dev/dsk/c4t4849544143484920373730313036373530303136d0s2 77bootdisk@primary-vds01
add the virtual disk to the guest domain
ldm add-vdisk apps bootdisk@primary-vds01 ldom1
the virtual disk will be imprted as c0d0 which is the whole lun itself.
bind, start ldom 1 and install OS (i used jumpstart) and it partitioned the boot disk c0d0 as / 15GB, swap the remaining space (10GB)
when you run format, print command on both guest and primary domain on this disk you'll see the same slice/size information
Part Tag Flag Cylinders Size Blocks
0 root wm 543 - 1362 15.01GB (820/0/0) 31488000
1 swap wu 0 - 542 9.94GB (543/0/0) 20851200
2 backup wm 0 - 1362 24.96GB (1363/0/0) 52339200
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
I havent used DMP but HDLM (Hitachi Dynamic link manager) seems not supported by ldom as i cannot make it work :(
I have no answer on your next question unfortunately.

Live upgrade only for zfs root?

Similar Messages

Maybe you are looking for