Got another slightly unhelpful message you might be able to explain:
# pkg image-update --be-name b134b DOWNLOAD PKGS FILES XFER (MB) Completed 1601/1601 33161/33161 666.0/666.0 pkg: Unable to clone the current boot environment. # beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- b134 NR / 14.92G static 2010-11-18 19:14 Oddly, zfs list -t snapshot shows no snapshots of the root pool. Here's the history: Identical machines A and B both running some ancient version of OpenSolaris. One was updated to snv126 and cloned to the other. A was image-updated to snv134 and has been running forever. B has multiple boot disks and was running both snv126 and sxce124. It was this snv126 that failed to update to snv134b even though its twin had updated to snv134 with no problem. I gave up on the snv126->snv134b update, cloned the working snv134 after zpool delete, rebooted, deleted all snapshots, and ran pkg image-update as above. # BE_PRINT_ERR=true beadm create test be_mount_callback: failed to mount dataset rpool/ROOT/test/opt at /tmp/.be.J6aqBc/opt: directory is not empty be_mount: failed to mount BE (test) on /tmp/.be.J6aqBc be_copy: failed to mount newly created BE be_get_uuid: failed to get uuid property from BE root dataset user properties. be_copy: destroying partially created boot environment be_get_uuid: failed to get uuid property from BE root dataset user properties. Unable to create test. Mount failed. # zfs get sharenfs rpool rpool/ROOT rpool/ROOT/b134 NAME PROPERTY VALUE SOURCE rpool sharenfs off default rpool/ROOT sharenfs off default rpool/ROOT/b134 sharenfs off default # zfs get sharesmb rpool rpool/ROOT rpool/ROOT/b134 NAME PROPERTY VALUE SOURCE rpool sharesmb off default rpool/ROOT sharesmb off default rpool/ROOT/b134 sharesmb off default /opt does have lots of stuff in it... Thanks _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
