gerard henry wrote: > hello all, > i have the same problem that: > http://opensolaris.org/jive/thread.jspa?threadID=73891&tstart=0 > > after reading this post, i deleted all the ancient BE, but still refuses > to activate new BE. What i notice is that, even if i can boot into b98, > the /opt dataset is empty, and the mountpoint is very strange. > Finally, i rebooted into b97, and try to delete the BE b98, just to > restart the upgrade. > b97 is called opensolaris-2 > b98 is called opensolaris-4 > > i'am in STEP1, after booting b98 (yes b98 is bootable), and as i noticed > that /opt is empty, i tried to modify the mountpoint. That explains the > mountpoints for opensolaris-4 > --------- > STEP1 > --------- > bash-3.2$ zfs list > NAME USED AVAIL > REFER MOUNTPOINT > rpool 16.4G > 2.72G 62K /rpool > [EMAIL PROTECTED] 19.5K > - 55K - > rpool/ROOT 8.90G > 2.72G 18K /rpool/ROOT > rpool/[EMAIL PROTECTED] 15K > - 18K - > rpool/ROOT/opensolaris-2 24.6M 2.72G > 4.44G legacy > rpool/ROOT/opensolaris-2/opt 825K 2.72G > 2.29G /opt > rpool/ROOT/opensolaris-4 8.88G 2.72G > 4.47G /tmp/tmpSFVCKC > rpool/ROOT/[EMAIL PROTECTED] 1.63G - > 2.22G - > rpool/ROOT/[EMAIL PROTECTED]:-:2008-09-19-20:05:57 497M - > 4.44G - > rpool/ROOT/opensolaris-4/opt 2.29G 2.72G > 2.29G /opt > rpool/ROOT/opensolaris-4/[EMAIL PROTECTED] 230K - > > 3.60M - > rpool/ROOT/opensolaris-4/[EMAIL PROTECTED]:-:2008-09-19-20:05:57 0 > - > 2.29G - > rpool/apps 262M > 2.72G 262M /usr/local > rpool/export 7.25G > 2.72G 19K /export > rpool/[EMAIL PROTECTED] 15K > - 19K - > rpool/export/home 7.25G 2.72G > 6.98G /export/home > rpool/export/[EMAIL PROTECTED] 19K > - 21K - > rpool/export/[EMAIL PROTECTED] 284M > - > 5.04G - > --------- > STEP2 > --------- > bash-3.2$ pfexec zfs set mountpoint=/tmp/tmpSFVCKC/opt > rpool/ROOT/opensolaris-4/opt > > --------- > STEP3 > --------- > bash-3.2$ pfexec beadm activate opensolaris-4 > Unable to activate opensolaris-4. opensolaris-4 does not exist or appear > to be a valid BE. > Please check that the name of the BE provided is correct. >
This looks really interesting . > bash-3.2$ beadm list > BE Active Mountpoint Space Policy Created > -- ------ ---------- ----- ------ ------- > opensolaris-2 N / 25.42M static 2008-09-12 10:40 > opensolaris-4 R - 13.28G static 2008-09-19 22:05 > bash-3.2$ pfexec beadm destroy opensolaris-4 > Are you sure you want to destroy opensolaris-4? This action cannot be > undone(y/[n]): y > The BE that was just destroyed was the 'active on boot' BE. > opensolaris-2 is now the 'active on boot' BE. Use 'beadm activate' to > change it. > Unable to destroy opensolaris-4. BE promotion failed. > bash-3.2$ pfexec beadm activate opensolaris-2 > Unable to activate opensolaris-2. BE promotion failed. > > How can i repair that? > The inherent problem is a zfs miscalculation that prevents the dataset promotion from succeeding even though you have plenty of space to do the promotion. That zfs bug is fixed in 98. Since you're running 97 here, the only thing I can suggest is to free up some space. It looks like your [EMAIL PROTECTED] snapshot has grown to 1.6G. If you don't plan on ever rolling back to the initial state of the system when it was first installed (build 86), then you should destroy it and try your commands again. # beadm destroy [EMAIL PROTECTED] -ethan > thanks in advance, > > gerard > > _______________________________________________ > indiana-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
