Reply to Evan Layton: Evan Layton wrote: > Can you provide the output from > zfs list > zfs list -o name,mountpoint,mounted I also include 'beadm list' which shows that "opensolaris-2" is the active BE. "opensolaris-3" was the new one created during image-update but it was destroyed following failed update.
Looks like "opensolaris2" lives in a strange place "/tmp/mnt3509" which I guess was created when I performed the interim update to b101b a while ago (which has since been very stable) I am guessing that this causes "opensolaris-3" to be mounted in the wrong place which then fails at the image-update step - hence suggestion that I try to build a new BE manually in a sensible place. (although it looks like it tried to mount in "/tmp/.be.LQaGAd" which seems sensible enough # beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris - - 10.23M static 2008-06-03 12:44 opensolaris-1 - - 87.43M static 2008-06-25 17:42 opensolaris-2 NR / 12.15G static 2008-12-08 13:41 # zfs list NAME USED AVAIL REFER MOUNTPOINT rpool 24.1G 32.5G 62K /rpool rpool/ROOT 9.98G 32.5G 18K /rpool/ROOT rpool/ROOT/opensolaris 9.71M 32.5G 2.46G legacy rpool/ROOT/opensolaris-1 86.9M 32.5G 2.81G legacy rpool/ROOT/opensolaris-1/opt 515K 32.5G 516M /opt rpool/ROOT/opensolaris-2 9.89G 32.5G 5.77G /tmp/mnt3509 rpool/ROOT/opensolaris-2/opt 932M 32.5G 484M /tmp/mnt3509/opt rpool/ROOT/opensolaris/opt 531K 32.5G 516M /opt rpool/export 14.1G 32.5G 19K /export rpool/export/home 14.1G 32.5G 14.1G /export/home # zfs list -o name,mountpoint,mounted NAME MOUNTPOINT MOUNTED rpool /rpool yes rpool/ROOT /rpool/ROOT yes rpool/ROOT/opensolaris legacy no rpool/ROOT/opensolaris-1 legacy no rpool/ROOT/opensolaris-1/opt /opt no rpool/ROOT/opensolaris-2 /tmp/mnt3509 yes rpool/ROOT/opensolaris-2/opt /tmp/mnt3509/opt no rpool/ROOT/opensolaris/opt /opt no rpool/export /export yes rpool/export/home /export/home yes root at paw-opensolaris-2008.05:~# > Also if the dataset rpool/ROOT/opensolaris-3/opt is not currently > mounted is there any data in /opt of your currenty booted BE > (opensolaris-3). BE "opensolaris-3" was created and then destroyed during the failed update. It's not clear why a new BE created by image-update would not be created correctly and would fail in this way. No obvious problems with disk space or anything like that. > http://defect.opensolaris.org/bz/show_bug.cgi?id=1156 Don't think this helps, it doesn't get as far as booting, the image-update step fails. P, ... -- This message posted from opensolaris.org
