Smpatch add -b fails for ZFS root

Question

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
#

Answer 1

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.