I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade.
Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less space (but in alternate BE). It seems its snapshot is taking too much space. I am not sure, how to fix this issue.
PHP Code:
root@oraprod_sap21:/# zoneadm list -icv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
1 oraprod_sap21-zesbr01 running /zone/oraprod_sap21-zesbr01/root native shared
3 oraprod_sap21-zesbq01 running /zone/oraprod_sap21-zesbq01/root native shared
root@oraprod_sap21:/# df -h | grep -i root
rpool/ROOT/s10s_u9wos_14a 274G 11G 216G 5% /
rpool/ROOT/s10s_u9wos_14a/var 274G 21G 216G 9% /var
zesbq01_root_pool 17G 21K 53M 1% /zesbq01_root_pool
zesbr01_root_pool 17G 21K 80M 1% /zesbr01_root_pool
zesbq01_root_pool/root 17G 6.9G 10G 41% /zone/oraprod_sap21-zesbq01/root
zesbr01_root_pool/zone 17G 6.2G 11G 37% /zone/oraprod_sap21-zesbr01/root
root@oraprod_sap21:/# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
old_patch yes yes yes no -
19_march yes no no yes -
root@oraprod_sap21:/# cd /var/tmp/10_Recommended
root@oraprod_sap21:/var/tmp/10_Recommended# ./installpatchset -B 19_march --s10patchset
Setup
..................
Recommended OS Patchset Solaris 10 SPARC (2013.01.29)
Application of patches started : 2013.03.19 23:12:28
Application of patches finished : 2013.03.19 23:12:28
The following filesystems have available space less than the recommended limit
to safely continue installation of this patch set :
/.alt.19_march/zone/oraprod_sap21-zesbq01/root-19_march (zesbq01_root_pool/root-19_march) : 54513kb available, 1260901kb recommended
/.alt.19_march/zone/oraprod_sap21-zesbr01/root-19_march (zesbr01_root_pool/zone-19_march) : 80976kb available, 1252637kb recommended
The recommended limit is an estimated upper bound on the amount of space an
individual patch application operation may require to complete successfully.
Due to the way the recommended limit is estimated, it will always be greater
than the actual amount of space required, sometimes by a significant margin.
Note the recommended limit is neither the exact amount of free space required
to apply a patch, or the amount of free space to completely install the
bundle, these interpretations are incorrect.
If the operator wishes to continue installation of this patch set at their own
risk, space checking can be overridden by invoking this script with the
'--disable-space-check' option.
Install log files written :
/.alt.19_march/var/sadm/install_data/s10s_rec_patchset_short_2013.03.19_23.12.28.log
/.alt.19_march/var/sadm/install_data/s10s_rec_patchset_verbose_2013.03.19_23.12.28.log
root@oraprod_sap21:/var/tmp/10_Recommended#
root@oraprod_sap21:/# cd /
root@oraprod_sap21:/# zfs list | grep -i 19_march
rpool/ROOT/19_march 917M 216G 10.6G /
rpool/ROOT/19_march/var 483M 216G 21.8G /var
rpool/ROOT/s10s_u9wos_14a@19_march 26.6M - 10.7G -
rpool/ROOT/s10s_u9wos_14a/var@19_march 46.9M - 21.3G -
zesbq01_root_pool/root@19_march 34.7M - 6.87G -
zesbq01_root_pool/root-19_march 301M 53.5M 6.70G /zone/oraprod_sap21-zesbq01/root-19_march
zesbr01_root_pool/zone@19_march 33.1M - 6.22G -
zesbr01_root_pool/zone-19_march 275M 79.3M 6.29G /zone/oraprod_sap21-zesbr01/root-19_march
Please suggest, how to fix this issue.
03-21-2013
