On 11/19/10 01:42, Shawn Walker wrote:
If you have multiple BEs or ZFS datasets that share the same name that's going to confuse the heck out of libbe, which in turn is going to create problems for pkg(1).
Oh I really hope we don't have multiple BEs or ZFS datasets that share the same name! That would obviously very confusing :-).
I'd also note that split datasets are not supported currently. So you can't have /opt on its own filesystem and expect things to work correctly right now.
It must have worked at one time because obviously the original machine had successfully been updated to b134. For those with space constrained boot disks, are there any plans to support /opt on a separate filesystem? Shades of the old /var/pkg discussion :-)
Beyond that, I can't help you here. This is a tangled mess that's outside of my area of expertise.
OK. I got bigger boot disks so now /opt can be on the root pool. You absolutely must have at least 32GB for the root pool now. I suppose there's still no way to free up the 3GB that b134->b134b took up without deleting the snapshot that pkg made... # beadm list -a BE/Dataset/Snapshot Active Mountpoint Space Policy Created ------------------- ------ ---------- ----- ------ ------- b134 rpool/ROOT/b134 NR / 14.93G static 2010-11-18 19:14 rpool/ROOT/b134/opt - /opt 1.95G static 2010-11-18 19:29 That fixed it. Thanks for the help - it wasn't obvious that doing this would work and these experiments take so much time... Cheers -- Frank _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
