Ethan Quach wrote: > > 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] > bash-3.2$ pfexec beadm destroy [EMAIL PROTECTED] Are you sure you want to destroy [EMAIL PROTECTED] This action cannot be undone(y/[n]): y bash-3.2$ beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris-2 N / 25.45M static 2008-09-12 10:40 opensolaris-4 R - 10.03G static 2008-09-19 22:05
ok, now i want to destroy entirely the BE opensolaris-4, as i can restart the upgrade, but: 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. i don't understand. Does it make sense to use "zfs destroy" to delete all datasets related to opensolaris-4? thanks for your reply, gerard _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
