Sergey:

You ran into a known issue and it is in the release note for osol_124:

http://wikihome.sfbay.sun.com/spe-re/attach/OpenSolaris%2Fosol_relnotes_snv_124.txt

11221 beadm create core dumps on OpenSolaris 122 SPARC
http://defect.opensolaris.org/bz/show_bug.cgi?id=11221

        When using builds 122 or 123, an attempt to create a new boot
        environment (BE) via beadm(1M) or indirectly through "pkg
        image-update" may result in a "segmentation fault".

        Work-around: Boot into an earlier boot environment and then
        manually create the desired BE from there.  For example, to
        image-update from build 122 or 123 the following set of
        commands can be used

                <reboot into the earlier BE>
                u...@host$ pfexec beadm create -e <name of build 122 BE> \
                        <name of new BE>
                u...@host$ pfexec beadm mount <name of new BE> /mnt
                u...@host$ pfexec pkg -R /mnt image-update
                u...@host$ pfexec beadm unmount <name of new BE>
                u...@host$ pfexec beadm activate <name of new BE>

        At this point, the new BE can be booted into.


Sergey Sprogis wrote:
I have two Sparc machines: vulcan-241.sfbay  carrying OpenSolaris
 snv_123.

I tried to upgrade it to snv_124 by with

pkg image-update.

but it produced   Memory fault failure:

======================================
# pkg image-update
DOWNLOAD                                  PKGS       FILES    XFER (MB)
Completed                              659/659 20551/20551  477.7/477.7

Memory fault


# beadm list
BE            Active Mountpoint      Space  Policy Created
--            ------ ----------      -----  ------ -------
opensolaris   -      -               16.75M static 2009-08-20 11:57
opensolaris-3 NR     /               8.40G  static 2009-09-29 18:18
opensolaris-4 -      /tmp/.be.EfaWsi 0B     static 2009-10-06 10:30

========================================


core file is available from vulcan-241.sfbay machine as /core


The similar pkg image-update upgrade on my Intel machines works ok.

Is it a known issue, or should I file a bug trough bugster?

In latter case what would be the right category/subcategory
in bug report?

Thanks,

Sergey
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to