Are volume manager commands available inside non-global zones

My application requires usage of volume manager commands to create new filesystem, expand an existing file system inside the non-global zone. Is this supported?
Or the only option is to create filesystem in global zone and assign to non-global zones?

ArunZone wrote:
My application requires usage of volume manager commands to create new filesystem, expand an existing file system inside the non-global zone. Is this supported?No. There's no zone knowledege with SVM, so it must be restricted to the global zone only. If you could use ZFS instead, you could delegate a filesystem to a zone and create/modify within the zone.
Or the only option is to create filesystem in global zone and assign to non-global zones?If you must use SVM, yes.
Darren

Similar Messages

Setting up Network Printers that are available to non-global zones

I need to set-up a network printer that will be available to all zones. I assume that I need to set-up a print server in the global zone. Thus can anyone suggest the best to set this up or point me to the appropriate documentation?
Many thanks,
Jon.

Hi,
/zones/oracle-z is my root directory of the zone.
* add the device to the zone :
root@mpbxapp1 # zonecfg -z oracle-z
zonecfg:oracle-z> add device
zonecfg:oracle-z:device> set match=/dev/global/dsk/d12s0
zonecfg:oracle-z:device> end
zonecfg:oracle-z> add device
zonecfg:oracle-z:device> set match=/dev/global/rdsk/d12s0
zonecfg:oracle-z:device> end
zonecfg:oracle-z> exit
* add FS to NGZ's /etc/vfstab : ( You may omit this step, I don't know why but it works without this step :) )
root@mpbxapp1 # vi /zones/oracle-z/root/etc/vfstab
/dev/global/dsk/d12s0 /dev/global/rdsk/d12s0 /global/oracle ufs 1 no logging
* add FS to global zone's /etc/vfstab :
root@mpbxapp1 # vi /etc/vfstab
/dev/global/dsk/d12s0 /dev/global/rdsk/d12s0 /zonefs/oracle ufs 1 no logging
* set the FilesystemMountPoints property :
root@mpbxapp1 # /usr/cluster/bin/clresource set -p FilesystemMountPoints=/global/oracle:/zonefs/oracle oracle-hastp
Whit this configuration you may ensure that the FS is not directly accessible from master zone. Actually, it's accessible but with a different PATH. For example, for Oracle, from the master zone Oracle can not be started/stopped because the controlfile can not be accessed. :)
Hope this helps,
Murat

Management Access Rights from non global Zone

We have a Sun Cluster 3.2 on Solaris 10. The Managed Resources are Solaris Zones:
e.g Resgroup xx
- xx-hasp (Storage for the Zone Root)
- xx-lh (the Service Address for the zone)
- xx-sczbt (the Zone boot Resource)
- xx-sczsmf (a managed SMF Service in the Zone)
How do i allow an arbitrary non root user or group inside the zone xx allow to disable the monitor of the resource xx-sczsmf so he can for example perform maintenance on it?
I have a few restrictions:
- the user has no account in the global zone
- the user may be allowed to manage all resources which belong to his zone
- the user is not allowed to manage any resource of another zone.
I guess solaris.cluster.resource.admin will not do the trick :-(
Fritz

Well, seems I have to use the same 'hack' i used for a SC 3.1.
Create a user in the global zone which has exactly the allowed rights (with a Role)
Assign it a public key
Give the users which are allowed to perform this operation the matching private key, so they can execute the command over ssh in the global zone.
Not very elegant, but fulfills all my requirements.

Running commands across global and non-global zones

Other than using ssh and public key access, is there better way to run a command in both the global and non-global zone? I need to disable some services (svcadm disable ... ) in both the global and non-global zones.
Thanks,
Roger S.

You can run commands in the non-global zone with the "zlogin" command from the global zone.
Running commands in a non-global zone from a non global zone works only with ssh, (or any other method using network)

Non-Global Zones and startup scripts

Created a non-global zone on a Solaris 10 box.
Boots up ok and I can login with zlogin.
It doesn't seem to run any of the scripts in /etc/rc2.d or /etc/rc3.d
I know Solaris 10 uses "Service Management Facility" for most services now,
but could still run legacy scripts in /etc/init.d ?
Also I can't get sshd to start on the non-global zone.
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
# svcadm enable -t svc:/network/ssh:default
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
Anyone got any ideas?
Michael

These services are off-line in the non-global zone, which is why non of the
rc2.d or rc3.d scripts are being run:
offline Dec_12 svc:/milestone/multi-user-server:default
offline Dec_12 svc:/milestone/multi-user:default
Any idea how to enable these, and why they are offline?
Michael
Created a non-global zone on a Solaris 10 box.
Boots up ok and I can login with zlogin.
It doesn't seem to run any of the scripts in
/etc/rc2.d or /etc/rc3.d
I know Solaris 10 uses "Service Management Facility"
for most services now,
but could still run legacy scripts in /etc/init.d ?
Also I can't get sshd to start on the non-global
zone.
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
# svcadm enable -t svc:/network/ssh:default
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
Anyone got any ideas?
Michael

Non-global zones and unix sockets

Hello, I have a problem with local zones and unix socket sharing. I've created directory in global zone for ex. /zones/shared. Added it to zones via 'add fs, type=lofs' . In one zone I'm putting mysql socket in it and I want that other local zones could use it. Is it possible to share socket between zones?
After all my experiments I'm always getting 'can't connect to mysql ... (146)' , 146 is 'connection refused' error.

These services are off-line in the non-global zone, which is why non of the
rc2.d or rc3.d scripts are being run:
offline Dec_12 svc:/milestone/multi-user-server:default
offline Dec_12 svc:/milestone/multi-user:default
Any idea how to enable these, and why they are offline?
Michael
Created a non-global zone on a Solaris 10 box.
Boots up ok and I can login with zlogin.
It doesn't seem to run any of the scripts in
/etc/rc2.d or /etc/rc3.d
I know Solaris 10 uses "Service Management Facility"
for most services now,
but could still run legacy scripts in /etc/init.d ?
Also I can't get sshd to start on the non-global
zone.
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
# svcadm enable -t svc:/network/ssh:default
# svcs -a |grep ssh2
offline 11:44:58 svc:/network/ssh:default
Anyone got any ideas?
Michael

Userdel command is missing in non-global zone

Hi,
I am trying to remove a user account in one of the non-global zone. But the 'userdel' command is missing in the system. This system is non-global zone. I am able to remove the same account in other non-global zone. Please find the system details:
root@mars # uname -a
SunOS mars 5.9 Generic_Virtual sun4u sparc SUNW,Sun-Fire
Can you please let me know which package i have to install in this box to perform user admin activity.
Thanks,
Ram.

Hi.
Not.
df -h swap - will show how many total swap now available on whole system.
For check limit you can use for example:
prctl -n zone.max-swap -i process $$
Regards.

Why there are no /dev/mem, /dev/kmem on solaris10 non-global zones?

Hi All,
We have an application on SOLARIS10 that tries to open '/dev/kmem' using 'kvm_open' system call and after that it reads certain kernel virtual memory parameter values by using 'kvm_nlist' system call.
In solaris 10 non-global zones these calls are failing as /dev/kmem cannot be found. Is there any other way to access the kmem or kernel memory parameters on non-global zones?
What are the corresponding files for /dev/mem, /dev/kmem on non-global zones? We are interpreting /dev/mem and /dev/kmem files to get status and statistical information of the system on solaris.
This is urgent....Please help....
Thanks

Ravi-N wrote:
Hi All,
We have an application on SOLARIS10 that tries to open '/dev/kmem' using 'kvm_open' system call and after that it reads certain kernel virtual memory parameter values by using 'kvm_nlist' system call.What information are you trying to gather?
In solaris 10 non-global zones these calls are failing as /dev/kmem cannot be found. Is there any other way to access the kmem or kernel memory parameters on non-global zones? You can't access kernel parameters directly (it's difficult to keep somone with access to it from making changes that would be visible to other zones). But it might be possible to get the information you need another way. Zones aren't virtual machines, and you can't do everything in a non-global zone that you can in the global zone.
Darren

Non-Global Zones - how can I tell what the Global Zone is

Hi,
I have a host that I know is a non-global zone (ngz). I can ssh to the ngz as root or a non-privileged user.
But once there how do I know what the host name for the global zone is?
I could probably run a script from all global zones to report all running zones and so I'd know that way but I have a specific need to know from inside the ngz.
Thanks!
Brian

bdunbar wrote:
That's a built-in security feature; and I know of no way to circumvent this mechanism.
I had some hope that there was a way to 'see' at least the global-zone information from the zone. From the shell the 'zone' commands are available ..
:# zoneadm list -cv
ID NAME STATUS PATH
48 hostname_svn running / So it's at least aware that it is a zone, even if it can't tell me anything else about itself. I can still go the long way around to get the information for my need, thanks.
The global zone is the only thing that can see everything. The non-global zones can only see information specific to their zone.
This is by design and it really is a security mechanism. You don't want the zones running outside of their boundaries and information about the global zone (or any other zone) is outside the boundaries of a non-global zone.
Cheers,

Format disks in a non-global zone

Hi
Can i format a disk inside a non global zone which has been assigned (add device) to this non-global zone.
thanks

In order to allow managing his/her disk to the zone "administrator".
This is what i�ve got when i try to format the disk in the non-global zone:
AVAILABLE DISK SELECTIONS:
0. c4t600A0B8000179A5000002EFD42AFC76Fd0 <SUN-CSM100_R_FC-0610 cyl 20478 alt 2 hd 64 sec 64> sx2_v2
ssd22 at scsi_vhci0 slave 0
1. c4t600A0B8000179A5000002F0A4355CEE9d0 <SUN-CSM100_R_FC-0610 cyl 20478 alt 2 hd 64 sec 64>
ssd24 at scsi_vhci0 slave 0
Specify disk (enter its number): 1
selecting c4t600A0B8000179A5000002F0A4355CEE9d0
[disk unformatted]
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> format
Ready to format. Formatting cannot be interrupted.
Continue? yes
Beginning format. The current time is Thu Nov 10 12:59:50 2005
Inquiry failed
failed
Warning: Unable to get capacity. Cannot check geometry
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.

Why I "Cannot share fielsytems in non-global zones"?

Dear all,
I've succesfully configured a solaris zone (which for the pourpouse I've called "stefano" just as a test) perfeclty running.
I've just a problem while I'm trying to export a directory as command
share -F nfs -d "test" /export/home/stefano
if run inside the zone gets me this error:
share_nfs: Cannot share filesystems in non-global zones: /export/home/stefano
why it isn't possible to export a filesystem within a non-global zones?
Is there any trics to solve this issue?
Thanks for your attention, ciao everybody!
Stefano
Milan, Italy

buonstefano wrote:
I don't want to mount an NFS filesystem exported from the global zone
I want instead to share an NFS filesystem within a non-global zone in order to let it mount by some others machine.It simply can't be done today.
NFS interacts very tightly with the kernel. So enabling an NFS server means giving certain kernel level permissions. The simple way to let a non-global zone do this would break the security model of zones. I'm sure folks are working on other ways to do this, but it's not available at this time.
Non-global zones aren't allowed to do everything. This is one of the things they're not allowed to do.
The global zone can share a non-global-zone's data to let other machines mount it. But you need global zone privileges to make that occur. The non-global zone's administrator couldn't do it directly.
Darren

Adding a cdrw to a non-global zone

Hi all,
I am attempting to add a cdrw on a laptop running Solaris 10 to a
non-global zone via the following (after browsing the archives of this
list as well as related forums and documentation):
"cdrw -l" when run in the global zone reports
"/dev/rdsk/c1t0d0s2" as the sole CD writer attached. I have previously
burnt cdr(s) using this, so the functionality of the drive is not an issue.
I then proceeded to configure a zone, "zulu01", and added a device via
the following using zonecfg (I have omitted the other configuration data
which is standard, root path, standard inherit-pkg-dir)
"add device"
"set match=/dev/rdsk/*"
"end"
"commit"
"verify"
I then installed the zone
"zoneadm -z zulu01 install"
zoneadm does the usual and reports success.
I boot the zone
"zoneadm -z zulu01 boot"
and login via "zlogin -C zulu01"
Inside zulu01, running "cdrw -l"
reports "No CD Writers found."
a "ls /dev/rdsk" shows that c1t0d0s2 is present.
I am aware that adding such a device is not recommended, but it is
supposedly possible?
Please advise on what I am doing wrong, or is it not possible to add a
cdrw to a non-local zone?
Thanks in advance.
Regards,
Jeremy.

This should work. A shot in the dark: can you try with another tool than cdrw, cdrecord for example? Also make sure that volume management is not running in the global zone (/etc/init.d/volmgt stop).
Blaise

X Sessions to a non global zone

I am trying to enable a direct cde login to my local zone.
Since installing the zone I have looked for the cde-login.xml svc script under /var/svc/manifest/application/graphical-login, but it is only available in my global zone.
Is it safe to copy this to my local zone and start the service using "svcadm enable svc:/application/graphical-login/cde-login" or will this cause my global zone issues?

Hi Darren,
There is an error message in the log file regarding cde-login.xml but why, the file is identical as the ones all all the other servers, I have listed our cde-login.xml below
Thanks again
Neil
pkgadd: ERROR: source path </var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/reloc/
var/svc/manifest/application/graphical-login/cde-login.xml> is corrupt
pathname does not exist
ERROR: attribute verification of </zones/saturn/root/var/svc/manifest/applicatio
n/graphical-login/cde-login.xml> failed
pathname does not exist
Installation of <SUNWdtlog> on zone <saturn> partially failed.
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">

<service_bundle type='manifest' name='SUNWdtdte:dtlogin'>
<service
name='application/graphical-login/cde-login'
type='service'
version='1'>
<single_instance />
<dependency name='multi-user'
grouping='require_all'
restart_on='error'
type='service'>
<service_fmri value='svc:/milestone/multi-user:default'/>
</dependency>
<dependency name='sysconfig'
grouping='require_all'
restart_on='none'
type='service'>
<service_fmri value='svc:/milestone/sysconfig'/>
</dependency>
<exec_method
type='method'
name='start'
exec='lib/svc/method/svc-dtlogin'
timeout_seconds='60' />
<exec_method
type='method'
name='stop'
exec=':kill'
timeout_seconds='60' />
<exec_method
type='method'
name='refresh'
exec='/usr/dt/config/dtlogin.rc reset'
timeout_seconds='60' />
<property_group name='startd'
type='framework'>

<propval name='ignore_error'
type='astring' value='core,signal' />
</property_group>

<property_group name='general' type='framework'>
<propval name='action_authorization' type='astring'
value='solaris.smf.manage.dt.login' />
</property_group>

<property_group name='dtlogin' type='application'>
<propval name='debug_level' type='count' value='0' />
<propval name='debug_log' type='astring' value='' />
<propval name='args' type='astring' value='' />
<propval name='value_authorization' type='astring'
value='solaris.smf.value.cde.login' />
</property_group>
<instance name='default' enabled='false'>
</instance>
<stability value='Unstable' />
<template>
<common_name>
<loctext xml:lang='C'>
CDE login
</loctext>
</common_name>
<documentation>
<manpage title='dtlogin' section='1'
manpath='/usr/dt/share/man' />
</documentation>
</template>
</service>
</service_bundle>

Non-global zone networking

I've created a non-global zone with a pair of anet devices. I plan to do IPMP inside the non-global zone to manage interface redundancy. The anet config is rather simple -- I have a net0 and net1 whose lower-link's are net2 and net3 respectively.
Inside the zone, it looks like everything is ready to go. My two VNICs are up.
zone# dladm show-link
LINK CLASS MTU STATE OVER
net0 vnic 1500 up ?
net1 vnic 1500 up ?
So I try to plumb them (if I can still use that term).
zone# ipadm create-ip net0
zone# ipadm create-ip net1
zone# ipadm show-if
IFNAME CLASS STATE ACTIVE OVER
lo0 loopback ok yes --
net0 ip down no --
net1 ip down no --
That's strange -- why are they not up?
zone# ifconfig net0 up; ifconfig net1 up
zone# ipadm show-if
IFNAME CLASS STATE ACTIVE OVER
lo0 loopback ok yes --
net0 ip ok yes --
net1 ip ok yes --
Aaah. Much better. Now I can get on with my life.
# ipadm create-ipmp -i net0 -i net1 ipmp0
# ipadm create-addr -T static -a 192.168.1.104/24 ipmp0/v4
So my quesion is why did I have to resort to running an ifconfig up on these interfaces? ifconfig is dead to me -- or so I'd like to think. :)
What is the "right" way to deal with this problem?

Figured this out.
The issue was that I had just done a zlogin to the zone after it was built (which was 3 weeks ago). I had completely forgotten that I had not yet completed the system configuration so the svc:/milestone/config:default service was offline, along with it's many dependancies.
Basically I manually configured the network information before I had told the system config that I was going to do so.
Strange behaviour -- but that's what happens when you don't follow order of operation.

Lucreate and non-global zones

Hi - I'm trying to get my head around Live Upgrades now that I've switched to ZFS on Solaris 10 for our test servers. The problem I have is we have a number of non-global zones and when I ran the lucreate command I get a number of warnings:
lucreate -n CPU_2012-07
Analyzing system configuration.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <CPU_2012-07>.
Source boot environment is <10>.
Creating file systems on boot environment <CPU_2012-07>.
Populating file systems on boot environment <CPU_2012-07>.
Temporarily mounting zones in PBE <10>.
Analyzing zones.
WARNING: Directory </export/zones/tdukwxstestz01> zone <global> lies on a filesystem shared between BEs, remapping path to </export/zones/tdukwxstestz01-CPU_2012-07>.
WARNING: Device <rpool/export/zones/tdukwxstestz01> is shared between BEs, remapping to <rpool/export/zones/tdukwxstestz01-CPU_2012-07>.
WARNING: Directory </export/zones/tdukwbprepz01> zone <global> lies on a filesystem shared between BEs, remapping path to </export/zones/tdukwbprepz01-CPU_2012-07>.
WARNING: Device <rpool/export/zones/tdukwbprepz01> is shared between BEs, remapping to <rpool/export/zones/tdukwbprepz01-CPU_2012-07>.
Duplicating ZFS datasets from PBE to ABE.
Creating snapshot for <rpool/export/zones/tdukwbprepz01> on <rpool/export/zones/tdukwbprepz01@CPU_2012-07>.
Creating clone for <rpool/export/zones/tdukwbprepz01@CPU_2012-07> on <rpool/export/zones/tdukwbprepz01-CPU_2012-07>.
Creating snapshot for <rpool/export/zones/tdukwxstestz01> on <rpool/export/zones/tdukwxstestz01@CPU_2012-07>.
Creating clone for <rpool/export/zones/tdukwxstestz01@CPU_2012-07> on <rpool/export/zones/tdukwxstestz01-CPU_2012-07>.
Creating snapshot for <rpool/ROOT/10> on <rpool/ROOT/10@CPU_2012-07>.
Creating clone for <rpool/ROOT/10@CPU_2012-07> on <rpool/ROOT/CPU_2012-07>.
Creating snapshot for <rpool/ROOT/10/var> on <rpool/ROOT/10/var@CPU_2012-07>.
Creating clone for <rpool/ROOT/10/var@CPU_2012-07> on <rpool/ROOT/CPU_2012-07/var>.
Mounting ABE <CPU_2012-07>.
Generating file list.
Finalizing ABE.
Fixing zonepaths in ABE.
Unmounting ABE <CPU_2012-07>.
Fixing properties on ZFS datasets in ABE.
Reverting state of zones in PBE <10>.
Making boot environment <CPU_2012-07> bootable.
Population of boot environment <CPU_2012-07> successful.
Creation of boot environment <CPU_2012-07> successful.
So ALL my non-global zones live under /export/zones/<zonename> - what do all the WARNINGS mean?
I then applied the Oracle CPU, activated the ABE and shutdown the server. When it came back up non of the zones would start and this seems to be because now all the zonepaths and references to the zones are labelled with CPU_2012-07 on the end. Now I can edit the zone xml files to fix this but am sure this is not the recommended method and something I would prefer not to do.
So basically I think I have not set my ZFS resource pools up correctly to take into account my non-global zones and where I have created them.
My zfs list output looks like this now, unfortunately I don't have the output prior to me starting this work:
zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 91.2G 456G 106K /rpool
rpool/ROOT 9.06G 456G 31K legacy
rpool/ROOT/10 38.2M 456G 4.34G /.alt.10
rpool/ROOT/10/var 22.6M 24.0G 3.60G /.alt.10/var
rpool/ROOT/CPU_2012-07 9.02G 456G 4.34G /
rpool/ROOT/CPU_2012-07@CPU_2012-07 566M - 4.34G -
rpool/ROOT/CPU_2012-07/var 4.12G 456G 4.11G /var
rpool/ROOT/CPU_2012-07/var@CPU_2012-07 13.8M - 3.58G -
rpool/dump 2.00G 456G 2.00G -
rpool/export 5.94G 456G 35K /export
rpool/export/home 76.9M 23.9G 76.9M /export/home
rpool/export/zones 5.87G 456G 36K /export/zones
rpool/export/zones/tdukwbprepz01 21.7M 456G 323M /export/zones/tdukwbprepz01
rpool/export/zones/tdukwbprepz01-10 321M 31.7G 312M /export/zones/tdukwbprepz01-10
rpool/export/zones/tdukwbprepz01-10@CPU_2012-07 8.50M - 312M -
rpool/export/zones/tdukwxstestz01 29.6M 456G 5.49G /export/zones/tdukwxstestz01
rpool/export/zones/tdukwxstestz01-10 5.51G 26.5G 5.47G /export/zones/tdukwxstestz01-10
rpool/export/zones/tdukwxstestz01-10@CPU_2012-07 32.1M - 5.48G -
rpool/logs 8.23G 23.8G 8.23G /logs
rpool/swap 66.0G 458G 64.0G -
Any help would be greatly appreciated.
Thanks - Julian.

OK, so been tinkering with this. I'm not sure this is my exact problem but a few people have reported issues with the following package:
121430-xx
In that it gives the exact same WARNINGS when trying to create an ABE via lucreate and you have non-global zones. So one of the suggestions was to go back to an earlier version of this patch and then someone said it was fixed in version 71 of the patch. So I installed the very latest version 121430-81 and now it fails with a different error. Fortunately this time I have a screen shot of the before and after:
BEFORE:
bash-3.2# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
1 build14 running /export/zones/build14 native shared
bash-3.2# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 70.0G 477G 106K /rpool
rpool/ROOT 1.98G 477G 31K legacy
rpool/ROOT/10 1.98G 477G 1.95G /
rpool/ROOT/10/var 28.8M 24.0G 28.8M /var
rpool/dump 2.00G 477G 2.00G -
rpool/export 36.5M 477G 33K /export
rpool/export/home 35K 24.0G 35K /export/home
rpool/export/zones 36.4M 477G 32K /export/zones
rpool/export/zones/build14 36.4M 32.0G 36.4M /export/zones/build14
rpool/logs 3.78M 32.0G 3.78M /logs
rpool/swap 66.0G 543G 16K -
bash-3.2# df -h |grep rpool
rpool/ROOT/10 547G 1.9G 477G 1% /
rpool/ROOT/10/var 24G 29M 24G 1% /var
rpool/export 547G 33K 477G 1% /export
rpool/export/home 24G 35K 24G 1% /export/home
rpool/export/zones 547G 32K 477G 1% /export/zones
rpool/export/zones/build14 32G 36M 32G 1% /export/zones/build14
rpool/logs 32G 3.8M 32G 1% /logs
rpool 547G 106K 477G 1% /rpool
bash-3.2# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
10 yes yes yes no -
bash-3.2# lucreate -n 10-CPU_2012_07
Analyzing system configuration.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <10-CPU_2012_07>.
Source boot environment is <10>.
Creating file systems on boot environment <10-CPU_2012_07>.
Populating file systems on boot environment <10-CPU_2012_07>.
Temporarily mounting zones in PBE <10>.
Analyzing zones.
Duplicating ZFS datasets from PBE to ABE.
Creating snapshot for <rpool/ROOT/10> on <rpool/ROOT/10@10-CPU_2012_07>.
Creating clone for <rpool/ROOT/10@10-CPU_2012_07> on <rpool/ROOT/10-CPU_2012_07>.
Creating snapshot for <rpool/ROOT/10/var> on <rpool/ROOT/10/var@10-CPU_2012_07>.
Creating clone for <rpool/ROOT/10/var@10-CPU_2012_07> on <rpool/ROOT/10-CPU_2012_07/var>.
Mounting ABE <10-CPU_2012_07>.
Generating file list.
Copying data from PBE <10> to ABE <10-CPU_2012_07>.
100% of filenames transferred
Finalizing ABE.
Fixing zonepaths in ABE.
Unmounting ABE <10-CPU_2012_07>.
Fixing properties on ZFS datasets in ABE.
Reverting state of zones in PBE <10>.
Making boot environment <10-CPU_2012_07> bootable.
ERROR: Unable to mount zone <build14> in </.alt.tmp.b-0ob.mnt>.
zoneadm: zone 'build14': zone root /export/zones/build14/root already in use by zone build14
zoneadm: zone 'build14': call to zoneadmd failed
ERROR: Unable to mount non-global zones of ABE <10-CPU_2012_07>: cannot make ABE bootable.
ERROR: umount: /.alt.tmp.b-0ob.mnt/var/run busy
ERROR: cannot unmount </.alt.tmp.b-0ob.mnt/var/run>
ERROR: failed to unmount </.alt.tmp.b-0ob.mnt/var/run>
ERROR: cannot fully unmount boot environment - <1>: file systems remain mounted
ERROR: Unable to make boot environment <10-CPU_2012_07> bootable.
ERROR: Unable to populate file systems on boot environment <10-CPU_2012_07>.
Removing incomplete BE <10-CPU_2012_07>.
ERROR: Cannot make file systems for boot environment <10-CPU_2012_07>.
bash-3.2# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
10 yes yes yes no -
10-CPU_2012_07 no no no yes -
So the very latest Live Upgrade patch doesn't seem to have fix this, I get even more errors now.
Again any help would be greatly appreciated.
Thanks - Julian.

Are volume manager commands available inside non-global zones

Similar Messages

Maybe you are looking for