(原创) 利用lucreate克隆V880的系统盘详细过程

susbin

More testing on the same V250:

# lustatus
ERROR: No boot environments are configured on this system
ERROR: cannot determine list of all boot environment names
#
# mv lutab-saved lutab
#
# lustatus
ERROR: cannot determine current boot environment name
ERROR: cannot determine status of boot environment <d0_0518>
ERROR: cannot determine current boot environment name
ERROR: cannot determine status of boot environment <t10s3_0604>
#
# mv lu-saved lu
#
# lustatus
Boot Environment           Is       Active Active    Can    Copy      
Name                       Complete Now    On Reboot Delete Status   
-------------------------- -------- ------ --------- ------ ----------
d0_0518                    yes      yes    yes       no     -         
t10s3_0604                 yes      no     no        yes    -         
#

shyjack

Yes, for the current primary BE, I used to remove /etc/lutab to destory it and it works very well for me, though better to find something from the offical doco.

Another tip Im used to is , normally, I will try to mount it before I kick off the activation.

lumount <BE name>, afterwards you can play around in the new BE with the running of the old BE,  like checking upgrade log, checking package etc.

luumount <BE name> and then do the activation.

jnsd

我试验过从SOLARIS 9 LU 到SOLARIS 10，感觉问题还是比较多。

SUN的工程师也认为这种情况下，还是整体重装比较可靠。

我个人认为，这适合同一套机器上测试两种版本的系统；还有就是小规模的更新，如补丁测试之类的。

shyjack

for live upgrade from sol9 to sol10, another discrepency is that you can apply cluster patch against the new sol10 boot environment.

According to the errors we got, is that some patches might intend go to the local zones, which sol9 is not supporting.

But if you run live upgrade from sol10 (say 11/06) to sol10 (08/07), it is convenient to online apply the cluster patch.