Re: [zones-discuss] update from 111b to 134
Hi, That works for me. Thanks, On Wed, Mar 17, 2010 at 4:30 PM, Jerry Jelinek gerald.jeli...@sun.com wrote: On 03/17/10 09:16 AM, Piotr Jasiukajtis wrote: The zone was installed and running before the update. System was upgraded by using 'pkg image-update'. No different actions ware done. In that case, the zone is in an undefined state and unusable. See: http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008 and the ipkg(5) man page. This situation is a temporary problem until the full zones support is provided with IPS. Jerry On Wed, Mar 17, 2010 at 3:58 PM, Jerry Jelinekgerald.jeli...@sun.com wrote: On 03/17/10 08:21 AM, Piotr Jasiukajtis wrote: Hi, After upgrade from 111b to b134 non local zone is not able to run properly. Was this a newly installed zone or one that existed from before the upgrade? If it was a pre-existing zone, did you upgrade the software inside the zone to be in sync with the global zone? If so, how? Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org -- Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] update from 111b to 134
Hi, After upgrade from 111b to b134 non local zone is not able to run properly. file: /zones/repo1/root/sbin/zfs initial argv: /usr/sbin/zfs mount -va threading model: native threads status: process terminated by SIGABRT (Abort), pid=29066 uid=0 code=-1 $C 08046b78 libc_hwcap2.so.1`_lwp_kill+7(1, 6, 8046b98, fee5ab6e) 08046b98 libc_hwcap2.so.1`raise+0x22(6, 0, 8046be8, fee31fea) 08046be8 libc_hwcap2.so.1`abort+0xf2(8046c18, fedc5000, 8046c18, 8098670, 8098a70, 400) 08046c18 libzfs.so.1`zfs_verror+0xd5(8098648, 80f, fedad934, 8046c4c) 08046c38 libzfs.so.1`zfs_standard_error_fmt+0x1ea(8098648, , fedad934, fedb11b0, 8098648) 08046c58 libzfs.so.1`zfs_standard_error+0x28(8098648, , fedb11b0, fed60d08) 08047cd8 libzfs.so.1`namespace_reload+0x430(8098648, 1, 0, fed610ea) 08047d18 libzfs.so.1`zfs_iter_root+0x20(8098648, 8059090, 8047d30, 0) 08047d58 get_all_datasets+0x9a(1, 8047d88, 8047d8c, 1) 08047dc8 share_mount+0x46d(2, 2, 8047e64, 8047f12, 8047e60, 3) 08047de8 zfs_do_mount+0x13(2, 8047e64, 8047e60, 807187c) 08047e28 main+0x2af(3, 8047e60, 8047e70, 8047e1c) 08047e54 _start+0x7d(3, 8047f04, 8047f12, 8047f18, 0, 8047f1c) # df -h Segmentation Fault (core dumped) # mount / on / read/write/setuid/devices/devic on Wed Mar 17 14:28:48 2010 # cat /var/svc/log/system-filesystem-local\:default.log [ Oct 13 03:39:19 Enabled. ] [ Oct 13 03:39:28 Rereading configuration. ] [ Oct 13 03:39:32 Executing start method (/lib/svc/method/fs-local). ] [ Oct 13 03:39:32 Method start exited with status 0. ] [ Oct 13 03:51:39 Stopping because service disabled. ] [ Oct 13 03:51:39 Executing stop method (null). ] [ Oct 13 12:51:46 Enabled. ] [ Oct 13 12:51:47 Executing start method (/lib/svc/method/fs-local). ] [ Oct 13 12:51:47 Method start exited with status 0. ] -- Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] update from 111b to 134
On 03/17/10 08:21 AM, Piotr Jasiukajtis wrote: Hi, After upgrade from 111b to b134 non local zone is not able to run properly. Was this a newly installed zone or one that existed from before the upgrade? If it was a pre-existing zone, did you upgrade the software inside the zone to be in sync with the global zone? If so, how? Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] update from 111b to 134
The zone was installed and running before the update. System was upgraded by using 'pkg image-update'. No different actions ware done. On Wed, Mar 17, 2010 at 3:58 PM, Jerry Jelinek gerald.jeli...@sun.com wrote: On 03/17/10 08:21 AM, Piotr Jasiukajtis wrote: Hi, After upgrade from 111b to b134 non local zone is not able to run properly. Was this a newly installed zone or one that existed from before the upgrade? If it was a pre-existing zone, did you upgrade the software inside the zone to be in sync with the global zone? If so, how? Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org -- Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] update from 111b to 134
On 03/17/10 09:16 AM, Piotr Jasiukajtis wrote: The zone was installed and running before the update. System was upgraded by using 'pkg image-update'. No different actions ware done. In that case, the zone is in an undefined state and unusable. See: http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008 and the ipkg(5) man page. This situation is a temporary problem until the full zones support is provided with IPS. Jerry On Wed, Mar 17, 2010 at 3:58 PM, Jerry Jelinekgerald.jeli...@sun.com wrote: On 03/17/10 08:21 AM, Piotr Jasiukajtis wrote: Hi, After upgrade from 111b to b134 non local zone is not able to run properly. Was this a newly installed zone or one that existed from before the upgrade? If it was a pre-existing zone, did you upgrade the software inside the zone to be in sync with the global zone? If so, how? Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
