I'm back with the same adventure, now trying to again luupgrade that snv_77 
system with snv_93. (after playing with LU on a fresh-installed test server, we 
decided to leave alone the actively used server until we develop a migration 
procedure)

So, here's what we did this time:

1) Snapshotted the active root (rootpool/rootfs) in case of rollback.
2) Disabled zones and moved their configs away (so that the system packages we 
plan to update are updated faster, without in-zone checks and replacements)
3) Updated SUNWlucfg SUNWlur SUNWluu SUNWluzone SUNWpkgcmdsr SUNWpkgcmdsu 
SUNWswmt and SUNWgrub in the snv_77 global zone
4) Made a snapshot again and a clone named rootpool/rootfs_snv93

Now trying to do the same "lucreate -c snv_77 -n snv_93" as we tried before, it 
complains and aborts as before, but this time we notice that it removed the 
mis-created /etc/lutab. So the next time we press Ctrl+S and grab a copy of 
this file for research. Here's the problem:

[b]# DO NOT EDIT THIS FILE BY HAND. This file is not a public interface.
# The format and contents of this file are subject to change.
# Any user modification to this file may result in the incorrect
# operation of Live Upgrade.
1:snv_77:C:0
1:/:rootpool/rootfs
rootpool/rootfs:1
1:boot-device:/dev/dsk/c3t1d0s0:2[/b]

Here, it recognized the root filesystem as "rootpool/rootfs
rootpool/rootfs" (that's two words with a linefeed in between; no idea why so)

We created the /etc/lutab file manually and fixed these file lines to read like 
this:

[b]1:snv_77:C:0
1:/:rootpool/rootfs:1
1:boot-device:/dev/dsk/c3t1d0s0:2[/b]

Now it seems to work, at least lustatus suddenly has a single configured BE :)

Then we still want the new BE. But "lucreate -n snv_93" fails again, so we 
update the manually created /etc/lutab to read like this:

[b]# DO NOT EDIT THIS FILE BY HAND. This file is not a public interface.
# The format and contents of this file are subject to change.
# Any user modification to this file may result in the incorrect
# operation of Live Upgrade.
1:snv_77:C:0
1:/:rootpool/rootfs:1
1:boot-device:/dev/dsk/c3t1d0s0:2
2:snv_93:C:0
2:/:rootpool/rootfs_snv93:1
2:boot-device:/dev/dsk/c3t1d0s0:2[/b]

Apparently, copy-paste transferred the snv_93 BE status as a complete FS, ready 
for booting. Since it's a zfs clone of a live system, that's somewhat true :)

Further tweaks included "zfs set mountpoint=legacy rootpool/rootfs_snv93", 
cleaning up /etc/lu/ICF.1 and /etc/lu/ICF.2 (the BEs were named "rootfs" 
instead of "snv_77" and "snv_93"), and copying /etc/lu/ and /etc/lutab over to 
the new BE (zfs clone).

After these tricks we have two BEs, lumount and luactivate works as well!

Now humming with "luupgrade -u -n snv_93 -s /mnt/cdrom", no errors reported, 
percents ticking...
 
 
This message posted from opensolaris.org
_______________________________________________
sysadmin-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss

Reply via email to