[OpenIndiana-discuss] Upgrade to oi_151a8 fails on one machine

[Jim Klimov]

On 2013-08-14 17:24, Richard Jones wrote:
> On Wed, Aug 14, 2013 at 01:35:04PM +0100, Richard Jones wrote:
>> On Wed, Aug 14, 2013 at 11:57:42AM +0100, Jon Tibble wrote:
>>> For debugging updates use the process here:
>>>
>>> http://wiki.openindiana.org/oi/Troubleshooting+image-update+failures
>>
>> Hi John, all,
>>
>> I'm having trouble with the update, though I suspect it's a local issue:
>
> [...]
>
> Relocated /var onto the rpool seems to fix things.

/var itself and much of its content must be part of the rootfs and
cloned by beadm, etc. You can seperate several paths onto different
storage, and the system's usability will be subject to ability to
mount that storage - such as:

rpool/SHARED                            154M  4.57G    31K  legacy
rpool/SHARED/var                        154M  1.85G    31K  legacy
rpool/SHARED/var/adm                   1.80M   498M    97K  legacy
rpool/SHARED/var/cores                  100M      0  99.9M  legacy
rpool/SHARED/var/crash                   50K  1.85G    32K  legacy
rpool/SHARED/var/log                   1.27M  1.85G  92.5K  legacy
rpool/SHARED/var/mail                   428K  1.90G   160K  legacy
rpool/SHARED/var/spool                  650K  1.85G    31K  legacy
rpool/SHARED/var/spool/clientmqueue     318K  1.85G  33.5K  legacy
rpool/SHARED/var/spool/mqueue           301K  1.85G    60K  legacy

I have systems which work with this well as an explicit mountpoint
and with canmount=noauto on structural pieces rpool/SHARED/var and
rpool/SHARED/var/spool; however with the non-legacy "zfs mount -a"
refusing to overlay non-empty directories, I prefer legacy and
/etc/vfstab for this job. There are also some changes for SMF
scripts which mount the filesystem structure, I think I described
them in the wiki or bugtracker... or intended to, at least...

//Jim