zfs discuss - Oct 2009 - heads up on SXCE build 125 (LU + mirrored root pools)

Hi everyone,

Currently, the device naming changes in build 125 mean that you cannot
use Solaris Live Upgrade to upgrade or patch a ZFS root dataset in a
mirrored root pool.

If you are considering this release for the ZFS log device removal
feature, then also consider that you will not be able to patch or
upgrade the ZFS root dataset in a mirrored root pool in this release
with Solaris Live Upgrade. Unmirrored root pools are not impacted.

OpenSolaris releases are not impacted by the build 125 device naming
changes.

I don''t have a CR yet that covers this problem, but we will keep you
posted.

Thanks,

Cindy

Is there a CR yet for this?

Thanks
Karl

Cindy Swearingen wrote:
>
> Hi everyone,
>
> Currently, the device naming changes in build 125 mean that you cannot
> use Solaris Live Upgrade to upgrade or patch a ZFS root dataset in a
> mirrored root pool.
>
> If you are considering this release for the ZFS log device removal
> feature, then also consider that you will not be able to patch or
> upgrade the ZFS root dataset in a mirrored root pool in this release
> with Solaris Live Upgrade. Unmirrored root pools are not impacted.
>
> OpenSolaris releases are not impacted by the build 125 device naming
> changes.
>
> I don''t have a CR yet that covers this problem, but we will keep
you
> posted.
>
> Thanks,
>
> Cindy
>
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


CONFIDENTIALITY NOTICE:  This communication (including all attachments) is
confidential and is intended for the use of the named addressee(s) only and
may contain information that is private, confidential, privileged, and
exempt from disclosure under law.  All rights to privilege are expressly
claimed and reserved and are not waived.  Any use, dissemination,
distribution, copying or disclosure of this message and any attachments, in
whole or in part, by anyone other than the intended recipient(s) is strictly
prohibited.  If you have received this communication in error, please notify
the sender immediately, delete this communication from all data storage
devices and destroy all hard copies.

Sorry, do you mean luupgrade from previous versions or from 125 to future
versions?

I luupgrade from 124 to 125 with mirrored root pool and everything is working
fine.
-- 
This message posted from opensolaris.org

Probably if you try to use any LU operation after you have upgraded to
build 125.

cs

On 10/23/09 16:18, Chris Du wrote:
> Sorry, do you mean luupgrade from previous versions or from 125 to future
versions?
> 
> I luupgrade from 124 to 125 with mirrored root pool and everything is
working fine.

Hi,

On Mon, Oct 19, 2009 at 05:03:18PM -0600, Cindy Swearingen
wrote:
> Currently, the device naming changes in build 125 mean that you cannot
> use Solaris Live Upgrade to upgrade or patch a ZFS root dataset in a
> mirrored root pool.
> [...]
Just ran into this yesterday... The change to get things going again
is ~ trivial:
>-1014: diff -u /usr/lib/lu/lulib{.ori,}
--- /usr/lib/lu/lulib.ori       Thu Oct 22 22:42:19 2009
+++ /usr/lib/lu/lulib   Sat Oct 24 01:21:41 2009
@@ -236,6 +236,7 @@
        start=`echo "$blob" | /usr/bin/grep -n "$lgzd_pool"
| head -2 | tail +2 | cut -d: -f1`
        start=`expr $start + 1`
        echo "$blob" | tail +$start | awk ''{print
$1}'' | while read dev; do
+           dev=`echo $dev | sed ''s/mirror.*/mirror/''`
            if [ -z "$dev" ]; then
               continue;
            elif [ "$dev" = "errors:" ]; then

With this "little hack" luactivate, lucreate and ludelete
(that''s what I just
tested) are working again...

YMMV

Kurt

What luupgrade do you use?
I uninstall lu package in current build first, then install new lu package in
the verion to upgrade.
-- 
This message posted from opensolaris.org

I think I finally see what you mean.

# luactivate b126
System has findroot enabled GRUB
ERROR: Unable to determine the configuration of the current boot environment
<b125>.
-- 
This message posted from opensolaris.org

On Thu, 5 Nov 2009, Chris Du wrote:
> I think I finally see what you mean.
> 
> # luactivate b126
> System has findroot enabled GRUB
> ERROR: Unable to determine the configuration of the current boot
environment <b125>.
Hmm.  Does this mean that lupgrading from b121 to b126 will also fail,
or is the problem specific to b125?

-- 
Rich Teer, SCSA, SCNA, SCSECA

URLs: http://www.rite-group.com/rich
      http://www.linkedin.com/in/richteer

Hi Rich,

In build 125, the device naming changed for redundant pools.

LU doesn''t understand the new device naming if you have a mirrored root
pool.

I believe an upgrade from 121 to 126 will be okay. Any LU operation on
your build 126 system will likely fail unless you follow Casper''s steps
for modifying LU scripts. Or, you detach your secondary mirrored disk,
run the LU operation, reattach the secondary mirrored disk. 

The CR is 6894189.

Cindy

----- Original Message -----
From: Rich Teer <rich.teer at rite-group.com>
Date: Thursday, November 5, 2009 4:47 pm
Subject: Re: [zfs-discuss] heads up on SXCE build 125 (LU + mirrored root pools)
To: Chris Du <dilidolo at gmail.com>
Cc: ZFS discuss <zfs-discuss at opensolaris.org>
> On Thu, 5 Nov 2009, Chris Du wrote:
> 
> > I think I finally see what you mean.
> > 
> > # luactivate b126
> > System has findroot enabled GRUB
> > ERROR: Unable to determine the configuration of the current boot 
> environment <b125>.
> 
> Hmm.  Does this mean that lupgrading from b121 to b126 will also fail,
> or is the problem specific to b125?
> 
> -- 
> Rich Teer, SCSA, SCNA, SCSECA
> 
> URLs: http://www.rite-group.com/rich
>       http://www.linkedin.com/in/richteer
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

On Thu, Nov 05, 2009 at 01:01:54PM -0800, Chris Du
wrote:
> I think I finally see what you mean.
> 
> # luactivate b126
> System has findroot enabled GRUB
> ERROR: Unable to determine the configuration of the current boot
environment <b125>.
A possible solution was posted in the thread:
  http://opensolaris.org/jive/thread.jspa?threadID=115503&tstart=0

-- 
albert chin (china at thewrittenword.com)

On Thu, Nov 05, 2009 at 03:39:56PM -0800, Rich Teer
wrote:
> On Thu, 5 Nov 2009, Chris Du wrote:
> 
> > I think I finally see what you mean.
> > 
> > # luactivate b126
> > System has findroot enabled GRUB
> > ERROR: Unable to determine the configuration of the current boot
environment <b125>.
> 
> Hmm.  Does this mean that lupgrading from b121 to b126 will also fail,
> or is the problem specific to b125?
The update doesn''t fail - just upgraded some of my machines yesterday.
But you have to apply the "little hack" I posted two weeks ago or so
(add dev=`echo $dev | sed ''s/mirror.*/mirror/''` after line
238) to
/usr/lib/lu/lulib which comes with b126, too, to get lu<xxxx> working
on mirrored root pools.

Hope this helps
Kurt

I just finished the upgrade.

detach one disk from the mirror, then luactivate b126 and init 6, after it
reboots, attach the disk to the mirror again, all went smoothly.

Thanks a lot.
-- 
This message posted from opensolaris.org

>On Thu, 5 Nov 2009, Chris Du wrote:
>
>> I think I finally see what you mean.
>> 
>> # luactivate b126
>> System has findroot enabled GRUB
>> ERROR: Unable to determine the configuration of the current boot
environment <b125>.
>
>Hmm.  Does this mean that lupgrading from b121 to b126 will also fail,
>or is the problem specific to b125?
>

Specific to b125 and later; you can fix this by editing
/usr/lib/lu/lulib

Casper

Seems like upgrading from b126 to b127 will have the same problem.
-- 
This message posted from opensolaris.org

> Seems like upgrading from b126 to b127 will have the
> same problem.
Yes, good point. I provided a blurb about this issue, here:

http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Live_Upgrade_Problem_.28Starting_in_Nevada.2C_build_125.29

Its a good idea to review this page whenever you are considering upgrading to
the next build.

Cindy
-- 
This message posted from opensolaris.org