[indiana-discuss] How to deal with /opt folder?

[Evan Layton]

Aubrey Li wrote:
> On Thu, Dec 4, 2008 at 12:43 PM, A. Stecker <as at kollerbeck.de> wrote:
>> some time ago i got the following answer to a similar (or maybe even the same) problem. haven't tried myself yet.
> 
> I'm doing exactly what the following suggested, which is sort of unreasonable.
> Can we treat /opt the same way as /export/home?

Not really since /opt is part of the BE since it can contain system data and 
/export/home is shared between BE's since it does not and should not contain 
system data.

> 
> Thanks anyway,
> -Aubrey
> 
>> Evan Layton wrote:
>>> It definitely looks like you've hit a similar issue as that described in 3452. To make sure of that we need to see if /opt is actually mounted and if you've ended up installing things into the /opt mount point directory when the BE boots it will fail to mount /opt on rpool/ROOT/<be_name>/opt and when a new BE is created it will have that same issue with /opt. Looking at the ZFS output you can see that the mount points for /opt in several BE's have more than one / in front of them which tends to indicate that there's been issues with mounting those datasets. To clean this issue up you'll need to move everything out of /opt zfs mount the rpool/ROOT/<be_name>/opt dataset and copy in what was moved out of /opt. Make sure that /opt is empty before attempting to mount the dataset.
>>>
>>> Also for those datasets affected the following zfs command can be used to clean up the mount point:
>>> # zfs set mountpoint=/opt rpool/ROOT/<be_name>/opt
>>>
>>> Thanks for your patience!
>>>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss