Whole root zone and fibre channel hba

I have Solaris 10 x86 loaded up on an IBM blade. I've created a whole root zone on it and have installed Symantec NetBackup 6.5.5 and configured it as Media Server. I have an SL8500 tape library in the environment and all the tape drives are fibre channel. Now, in the global zone, I can run fcinfo hba-port or scli and the global zone finds the hba's with no problem. I've added the /dev/cfg/c1 and /dev/cfg/c2 devices to the zone, but running the commands, it cannot find the hba's at all.
Is there something else that I need to do so that the zone can see the hba's, or is this just not possible in a zone?
Thanks in advance,
Ed Coates

Hi.
Check release notes for Netbackup. As i know Media Server is supported anly at Global zones.
You can add access to /dev/rmt/* and give access to tapes, but stiil problem with robot device and this configuration not supported.
Regards.

Similar Messages

Whole root zone and packages

I installed in my global zone the "Entire Distribution" of Solaris 10 and some software from Companion CD.
Now I would like install a "whole root zone" with a basic set of packages (like "End User Distribution") and without the packages
from the Companion CD.
I can use pkgrm to delete the unnecessary packages in my whole root zone.
But is there a more elegant way to get a whole root zone only with basic packages?
Regards. P.

The "easy" way would be to do a minimal installation in the Global zone and then install the required services in the local zone.
HTH,
Roger S.

Whole root or sparse root zones and patching

Hi all,
A while back, I did some cluster patching tests on a system with only sparse root zones, and one with whole root zones...and I seem to recall that the patch time was about equal which surprised me. I had thought the sparse root model mainly is patching the global zone, and even though patchadd may need to run through the sparse NGZ's...that it isn't doing much other than updating /var/sadm info in the NGZ's.
Has anyone seen this to be true or if there are major patching improvements using a "sparse" root NGZ model over a "whole" root model?
thanks much.

My testing showed the same results and I was a bit surprised as well. As I dug into it further my understanding was that the majority of the patch application time goes into figuring out what to patch, not actually copying files around. That work must be done for the sparse zones in the same way as for the full root zones, we just save the few milliseconds of actually backing up and replacing the file.
I suspect there is a large amount of slack that could be optimized in the patching process (both with and without zones), but I don't understand it nearly well enough to say that with any authority.

SMC - Solaris Management Console in whole root zone

Hi,
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.
Thanks...

Hi dnzrnd,
dnzrnd wrote:
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

Solaris Management Console in whole root zones

Is it possible to run smc in whole root zone? Is there a howto for this? I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.

Hi dnzrnd,
dnzrnd wrote:
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

SMC doesn't work in any solaris 10 whole-root zones

All
Are you aware of SUN not designing whole-root zones to work with Solaris Management Console?
None of my solaris 10 whole-root zones/containers will run Solaris Management Console. Very, very frustrating!
Anyone have a trick to get around this crazy design??
Thank you!
SB

Thanks for your help!
Yes, i see all font types.
But maybe i havn't explained my problem good enough:
I have a FLA-File which works great in Flash CS3: everything – even on different computers – is okay!
The same FLA-File on the same computer in Flash CS6: the font-rendering is broken!
In CS6 there seems to be a difference between textfields made via ActionScript and textfields on the stage: see the attached file in my first post.

Unable to create a whole root zone

Hi Folks,
I wanted to create a whole-root zone. I am unable to create one :(. Did some one encounter this problem ?.
BTW: I have SC 3.2 installed on this two node cluster. I was able to validate our Data services on this setup without any problem Now I am trying to experiment with zones, by creating zones. I am unable to move further with my validation of our data services on zones.
*) mkdir -m 700 /export/zone-1
*) The version of the OS used
# cat /etc/release
Solaris 10 11/06 s10s_u3wos_09 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 01 November 2006
# zonecfg -z zone-1
zone-1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-1> create
zonecfg:zone-1> remove inherit-pkg-dir dir=/sbin
zonecfg:zone-1> remove inherit-pkg-dir dir=/usr
zonecfg:zone-1> remove inherit-pkg-dir dir=/platform
zonecfg:zone-1> remove inherit-pkg-dir dir=/lib
zonecfg:zone-1> set autoboot=true
zonecfg:zone-1> set zonepath=/export/zone-1
zonecfg:zone-1> add net
zonecfg:zone-1:net> set address=192.18.75.237
zonecfg:zone-1:net> set physical=eri0
zonecfg:zone-1:net> end
zonecfg:zone-1> info
zonename: zone-1
zonepath: /export/zone-1
autoboot: true
pool:
limitpriv:
net:
address: 192.18.75.237
physical: eri0
zonecfg:zone-1> verify
zonecfg:zone-1> commit
zonecfg:zone-1> exit
# cat /etc/zones/zone-1.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">

<zone name="zone-1" zonepath="/export/zone-1" autoboot="true">
<network address="192.18.75.237" physical="eri0"/>
</zone>
# zoneadm list -civ
ID NAME STATUS PATH
0 global running /
- zone-1 configured /export/zone-1
# zoneadm -z zone-1 verify
# zoneadm -z zone-1 install
Preparing to install zone <zone-1>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-1> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWdtlog
system SUNWdtlog System boot for Desktop Login
# pkginfo -i SUNWsmmgr
system SUNWsmmgr System Management Agent Startup scripts
*** package <SUNWsczr> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/stoprgm> failed
pathname does not exist
NOTE: When the package <SUNWsczr> was installed in the global zone, the file <etc/init.d/stoprgm> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone <zone-1> in the file </export/zone-1/root/etc/init.d/stoprgm>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWsczr/save/pspool/SUNWsczr/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWsczr> on zone <zone-1> failed.
*** package <SUNWnisr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nis> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nis> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nis>.
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nisplus>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <lib/svc/method/nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nisplus>.
WARNING: attribute verification of </export/zone-1/root/var/nis/NIS+LDAPmapping.template> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <var/nis/NIS+LDAPmapping.template> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/nis/NIS+LDAPmapping.template>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ nis/client.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/nisplus.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/rex.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/nisplus.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rex.xml> failed
pathname does not exist
Installation of <SUNWnisr> on zone <zone-1> partially
failed.
*** package <SUNWypr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/var/yp/updaters> failed
pathname does not exist
NOTE: When the package <SUNWypr> was installed in the global zone,
the file <var/yp/updaters> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/yp/updaters>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/passwd.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/server.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/update.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/xfr.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/passwd.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/server.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/update.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/xfr.xml> failed
pathname does not exist
Installation of <SUNWypr> on zone <zone-1> partially
failed.
*** package <SUNWipplr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWipplr/save/pspool/SUNWipplr/reloc/var/svc/manifest/applic ation/print/ipp-listener.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/ipp-listener.xml> failed
pathname does not exist
Installation of <SUNWipplr> on zone <zone-1> partially
failed.
*** package <SUNWaccr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-sar> failed
pathname does not exist
NOTE: When the package <SUNWaccr> was installed in the global zone,
the file <lib/svc/method/svc-sar> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-sar>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWaccr/save/pspool/SUNWaccr/reloc/var/svc/manifest/system/s ar.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/sar.xml> failed
pathname does not exist
Installation of <SUNWaccr> on zone <zone-1> partially
failed.
*** package <SUNWbsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/rpld.conf> failed
pathname does not exist
NOTE: When the package <SUNWbsr> was installed in the global zone,
the file <etc/rpld.conf> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/rpld.conf>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/ra rp.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/rp c/bootparams.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rarp.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/bootparams.xml> failed
pathname does not exist
Installation of <SUNWbsr> on zone <zone-1> partially
failed.
*** package <SUNWdhcsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dhcp> failed
pathname does not exist
NOTE: When the package <SUNWdhcsr> was installed in the global zone,
the file <etc/init.d/dhcp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dhcp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWdhcsr/save/pspool/SUNWdhcsr/reloc/var/svc/manifest/networ k/dhcp-server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dhcp-server.xml> failed
pathname does not exist
Installation of <SUNWdhcsr> on zone <zone-1> partially
failed.
*** package <SUNWatfsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-autofs> failed
pathname does not exist
NOTE: When the package <SUNWatfsr> was installed in the global zone,
the file <lib/svc/method/svc-autofs> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-autofs>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWatfsr/save/pspool/SUNWatfsr/reloc/var/svc/manifest/system /filesystem/autofs.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/filesystem/autofs.xml> failed
pathname does not exist
Installation of <SUNWatfsr> on zone <zone-1> partially
failed.
*** package <SUNWkdcr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWkdcr/save/pspool/SUNWkdcr/reloc/var/svc/manifest/network/ security/krb5_prop.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/security/krb5_prop.xml> failed
pathname does not exist
Installation of <SUNWkdcr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.gif> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.gif> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.gif>.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.png> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.png> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.png>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWapch2r/save/pspool/SUNWapch2r/reloc/var/svc/manifest/netw ork/http-apache2.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/http-apache2.xml> failed
pathname does not exist
Installation of <SUNWapch2r> on zone <zone-1> partially
failed.
*** package <SUNWbindr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbindr/save/pspool/SUNWbindr/reloc/var/svc/manifest/networ k/dns/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dns/server.xml> failed
pathname does not exist
Installation of <SUNWbindr> on zone <zone-1> partially
failed.
*** package <SUNWbnur> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbnur/save/pspool/SUNWbnur/reloc/var/svc/manifest/network/ uucp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/uucp.xml> failed
pathname does not exist
Installation of <SUNWbnur> on zone <zone-1> partially
failed.
*** package <SUNWcnsr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ chargen.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ daytime.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ discard.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ echo.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ time.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/chargen.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/daytime.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/discard.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/echo.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/time.xml> failed
pathname does not exist
Installation of <SUNWcnsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/lp/fd/pr.fd> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <etc/lp/fd/pr.fd> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/lp/fd/pr.fd>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/print-svc> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <lib/svc/method/print-svc> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/print-svc>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWpsr/save/pspool/SUNWpsr/reloc/var/svc/manifest/applicatio n/print/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/server.xml> failed
pathname does not exist
Installation of <SUNWpsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/snmp/mib/sun.mib> failed
pathname does not exist
NOTE: When the package <SUNWsacom> was installed in the global zone,
the file <var/snmp/mib/sun.mib> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/snmp/mib/sun.mib>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.dmi> is corrupt
file size <373> expected <1125> actual
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.snmpdx& gt; is corrupt
file size <382> expected <685> actual
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.dmi> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.snmpdx> failed
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/dmi.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/snmpdx.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/dmi.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/snmpdx.xml> failed
pathname does not exist
Installation of <SUNWsacom> on zone <zone-1> partially
failed.
*** package <SUNWdtlog> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <etc/init.d/dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dtlogin>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <lib/svc/method/svc-dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-dtlogin>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWdtlog> on zone <zone-1> failed.
*** package <SUNWnfssr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nfs-server> failed
pathname does not exist
NOTE: When the package <SUNWnfssr> was installed in the global zone,
the file <lib/svc/method/nfs-server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nfs-server>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/rquota.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/rquota.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/server.xml> failed
pathname does not exist
Installation of <SUNWnfssr> on zone <zone-1> partially
failed.
*** package <SUNWntpr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/inet/ntp.server> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <etc/inet/ntp.server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/inet/ntp.server>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/xntp> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <lib/svc/method/xntp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/xntp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWntpr/save/pspool/SUNWntpr/reloc/var/svc/manifest/network/ ntp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ntp.xml> failed
pathname does not exist
Installation of <SUNWntpr> on zone <zone-1> partially
failed.
*** package <SUNWftpr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWftpr/save/pspool/SUNWftpr/reloc/var/svc/manifest/network/ ftp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ftp.xml> failed
pathname does not exist
Installation of <SUNWftpr> on zone <zone-1> partially
failed.
*** package <SUNWrcapr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcapr/save/pspool/SUNWrcapr/reloc/var/svc/manifest/system /rcap.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/rcap.xml> failed
pathname does not exist
Installation of <SUNWrcapr> on zone <zone-1> partially
failed.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcmdr/save/pspool/SUNWrcmdr/reloc/var/svc/manifest/networ k/talk.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/comsat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/finger.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/login.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rexec.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rstat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rusers.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/spray.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/wall.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/shell.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/talk.xml> failed
pathname does not exist
Installation of <SUNWrcmdr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> ; failed
pathname does not exist
NOTE: When the package <SUNWsmmgr> was installed in the global zone,
the file <etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> was also installed. Af

Hello,
I still get the errors.
# zonecfg -z zone-one
zone-one: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-one> create -b
zonecfg:zone-one> set autoboot=true
zonecfg:zone-one> set zonepath=/export/zone-one
zonecfg:zone-one> add net
zonecfg:zone-one:net> set physical=eri0
zonecfg:zone-one:net> set address=192.18.xx.xxx
zonecfg:zone-one:net> end
zonecfg:zone-one> verify
zonecfg:zone-one> commit
zonecfg:zone-one> exit
# zoneadm -z zone-one verify
# zoneadm -z zone-one install
Preparing to install zone <zone-one>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-one> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
_DD

Whole root zone doesn't run Solaris Management Console

All
I created a couple of Whole Root zone's, but the SMC is not working. It can't even be found. (However, on the "sparse" zones, it works fine.)
I ran:
pkginfo SUNWsmcmd
and got:
system SUNWsmcmd System Management Agent applications and utilities
So, it seems like it's installed, but it ain't working on any of the whole-root zones.
Anyone have any ideas on this one?
Thank you
SB

I think I have the same problem -
One global zone and one whole-root zone installed.
I access the server withhttps://servername:6789/containersthen I can see Solaris Container Manager 3.6.1but when I select it, I get
There was an error while connecting to the Solaris Container Manager service. Restart the services and login again.
Restart Sun Management Center services and log in again.I restarted meanwhile every service, but I did not a server reboot.
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   1 mantis-ldap      running        /var/zone/mantis-ldapWhat logfile could help to clarify that?
SMC release is 3.6.1
-- Nick

Whole root zone creation

Hi
I am building a whole root zone running Solaris U9 I noticed the   zone does not get installed with some updated packages from global zone like the openssl installed in global zone does not get installed in the non global zone and it also requires sshd user to be defined This results the ssh not starting in the new zone I want to know if this is the default behaviour of whole root zone installation process and how can we get the zone to be installed with all the currently running packages of the global zone Are there any post installation steps that need to be followed for the zone to boot up correctly. I have run the post post installation configuration steps as well
TIA

Thanks Walter
I was wondering since most of the packages installations at least require one interaction   where it asks for confirmation. how the other packages are getting installed. But mostly that might be the reason
There is also the SUNW_PKG_ALLZONES and other related variables   which control this but since here the packages which are already installed on global zome are getting installed on NG zone , how these parameters can be changed I could not found any of these parameters in any pkginfo file in the global zone

Replication whole root zones

Hello,
I need to configure whole root zones which needs to be replicated to a secondary site.
Would like to know if there is a way by which i can avoid replicating the swap file in a whole root zone configuration.
Please advice.
Thanks & Regards
Ranjit

I don't understand your question. What swap file are you referring to? There's nothing about a whole-root zone that requires a swap file be present.
Darren

Secure shell in a whole root zone

Hello,
I have two whole root zones running on my Solaris 10 server along with the global zone. I am able to secure shell in to the global zone, but not the whole root zones. Secure shell does not appear to be running in the whole root zones. I've tried svcadm restart ssh in the whole root zones,but no luck. What do I need to do to get secure shell working on the whole root zones?

to create the necessary keys -
# ssh-keygen -b 1024 -t rsa1 -f /etc/ssh/ssh_host_key -N ""
# ssh-keygen -b 1024 -t rsa -f /etc/ssh/ssh_host_rsa_key -N ""
# ssh-keygen -b 1024 -t dsa -f /etc/ssh/ssh_host_dsa_key -N ""-- Nick

Catalyst 4500 Ethernet and fibre channel passthru

dear sir,
anyone have any idea / documentation showing that the belows device 1.) & 2.) can support Ethernet and fibre channel passthru ? thanks.
1.) WS-X4424-GB-RJ4 (Catalyst 4500 24-port 10/100/1000 Module (RJ45)
2.) WS-X4306-GB (Catalyst 4500 Gigabit Ethernet Module, 6-Ports (GBIC)

You're welcome. Check below for the module info. And there is description about support of fibre channel passthru.
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_data_sheet0900aecd802109ea.html
You can also seach Cisco web for more info.
Hope this helps.

Patching JES in whole root zone (where JES never installed in global zone)

We ran into a problem today - we have a server (Solaris 10 x86 on 4150) with two full root zones. JES 5u1 was intsalled in each full root zone at a later date and never installed in the global zone. Now when trying to install the latest JES 5 patch cluster we have run into a problem. The patch cluster has a check that only lets it be run in the global zone. When we run it in the Global Zone - it exits every patch with a return code of 8 (software not installed).
Is there any way we can run the patch bundle so it applies the patches to the no-global zones in this case? Will now installing teh shared components in the global zone then allow the patch cluster to run sucessfully.
Thanks for any guidance here....

Solution was to manually edit the patch cluster installation script and comment out the global zone check - it then installed perfecttly fine in the whole root zone

How to identify fibre channel HBA working or not

Hi,
I dont know how to identify FC hba card and port. I cant access the box because it is in a remote location.
My customer is saying there is 3 hba cards and one is showing disconnected. I see three types of cards in path_to_inst file and luxadm -e port command.
I cant understand the connection between the controller which showing in the cfgadm command and hba device.
/devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl showing disconnected what does it mean?
So Please help me to find answers of these questions.
1) how many physical FC HBA cards are in this server.
2) How many FC Ports are in this server
3) Why controller C4 showing un configured.
4) why /devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl showing disconnected
logs :-
bash-3.00# fcinfo hba
fcinfo: invalid object
Usage: fcinfo [-?] <OBJECT> [-?] [<OPERAND>]
Usage by OBJECT:
fcinfo hba-port [OPTIONS] [<WWN ...>]
fcinfo remote-port <OPTIONS> [<WWN ...>]
For more information, please see fcinfo(1M)
bash-3.00# fcinfo hba-port
HBA Port WWN: 10000000c93aa32d
OS Device Name: /dev/cfg/c2
Manufacturer: Emulex
Model: LP9002L
Firmware Version: 3.90a7 (C2D3.90A7)
FCode/BIOS Version: Boot:3.20 Fcode:1.40a0
Serial Number: BG40340370
Driver Name: emlxs
Driver Version: 2.50o (2010.01.08.09.45)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c93aa32d
HBA Port WWN: 10000000c93ae1be
OS Device Name: /dev/cfg/c7
Manufacturer: Emulex
Model: LP9002L
Firmware Version: 3.92a3 (C2D3.92A3)
FCode/BIOS Version: Boot:3.20 Fcode:none
Serial Number: BG40855848
Driver Name: emlxs
Driver Version: 2.50o (2010.01.08.09.45)
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb
Current Speed: 2Gb
Node WWN: 20000000c93ae1be
HBA Port WWN: 210000e08b08c5c1
OS Device Name: /dev/cfg/c4
Manufacturer: QLogic Corp.
Model: QLA2200
Firmware Version: 02.01.145
FCode/BIOS Version: fcode: 0.00;
Serial Number: not available
Driver Name: qlc
Driver Version: 20090929-2.32
Type: unknown
State: offline
Supported Speeds: 1Gb
Current Speed: not established
Node WWN: 200000e08b08c5c1
bash-3.00#
bash-3.00# cat /etc/path_to_inst | grep -i fp
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0" 3 "fp"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900142,1" 0 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900142,2" 2 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900160,1" 3 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0/ssd@w5001738001900190,1" 4 "ssd"
"/ssm@0,0/pci@19,600000/lpfc@1/fp@1,0" 4 "fp"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@0,0" 1 "fp"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@0,0/ssd@w5001738001900170,1" 1 "ssd"
"/ssm@0,0/pci@1b,600000/lpfc@1/fp@1,0" 2 "fp"
"/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0" 5 "fp"
"/ssm@0,0/pci@1f,600000/QLGC,qla@1/fp@0,0" 0 "fp"
"/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0" 6 "fp"
"/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@1,0" 7 "fp"
bash-3.00# cfgadm -al | grep -i fc
c2 fc-fabric connected configured unknown
c4 fc connected unconfigured unknown
c7 fc-fabric connected configured unknown
bash-3.00# luxadm -e port
/devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:devctl CONNECTED
/devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:devctl NOT CONNECTED
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00#
bash-3.00# cfgadm -alv | grep -i fc
unavailable fc-fabric n /devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:fc
unavailable array-ctrl n /devices/ssm@0,0/pci@19,600000/lpfc@1/fp@0,0:fc::5001738001900142
unavailable fc n /devices/ssm@0,0/pci@1d,600000/QLGC,qla@1/fp@0,0:fc
unavailable fc-fabric n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc
unavailable array-ctrl n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc::5001738001900160
unavailable array-ctrl n /devices/ssm@0,0/pci@1f,600000/fibre-channel@1/fp@0,0:fc::5001738001900190
bash-3.00#

If you see state other than online, or speed "not established," the HBA is not working, but it may not be connected to anything.
If you think it is connected, get the WWN from the "HBA Port WWN" field, and run
fcinfo remote-port wwn
If you don't get any information back, you're not seeing any other FC devices (might be a switch zoning issue).
If you see other ports (usually their WWN starts with a 5), but not your LUNs, add -s, and you can see which LUNs have been masked (made available) to this WWN.
If you add -l, you can see the error counters for the link, which should be very low (single digit) and not increasing. If not, you might have a bad cable or SFP/GBIC.
Hope this helps!

Clarification on how to use Xserve Raid and Fibre Channel without xsan.

First let me apologize for not responding earlier to your response, I tend to get busy and then forget to check back here.
Tod, the answer to your question is No, only one computer is accessing the xserve raid files at any one time and that is via Fibre Channel. However I do have the xserve raids set up as share points via ethernet.
Maybe I should turn that off and only access the files with the one computer that can connect via fibre channel.
I never thought of that. I will try that while I await for your answer, thanks again.
Todd Buhmiller
I have the following setup:
Xserve: 2x2Ghz Dual Core Intel Xeon, 5Gb of Ram, Running 10.5.8 Leopard Server
Xserve Raid with firmware version 1.5.1/1.51c on both controllers, and
Qlogic Sanbox 5600
Apple Fibre Channel Cards in Xserve, and Mac Pro Tower; Apple 2 Port 4Gbs Fibre Channel Card
Mac Pro Tower-Quad Core Intel Xeon 2.8Ghz, 16Gb of Ram, Running Snow Leopard 10.6.4
Here is the problem.
The directory for the xserve raids keep getting corrup, and I use disc warrior to rebuild them. Is there a way to keep the directories from getting corrupt? I am a few pieces of equipment before I can build an Xsan as that is the ultimate goal, but until then, I just need to be able to have the raids funciton as storage without having to rebuild the directories all of the time.
Anybody have any suggestions?
Thanks
Todd Buhmiller
Widescreen Media
Calgary, Alberta Canada
Tod Kuykendall
Posts: 1,237
From: San Diego
Registered: Oct 11, 2000
Re: Xserve Raid Mounts, Corrupt Directory tired of rebuilding directory
Posted: Jun 27, 2010 1:25 PM in response to: Todd Buhmiller
Are multiple computers accessing the same data on the RAID at the same time?
If so then NO. This is the source of your data corruption and I'm surprised if you were able to get all your data back every time if this is how you've been running your system. Each fibre channel assumes it has full and sole control of every volume it has mounted, no data arbitration is practiced and data corruption will occur if this assumption is wrong.
The only way this set-up will work is to use partitions or LUN masks so the volumes are accessed by one computer at any time. As long as one computer relinquishes control before another mounts it you will dodge arbitration issues but this is a dangerous game. If you screw up and mount an already mounted volume - and there is no easy way to tell if a volume is mounted - corruption will then occur. Sharing data simultaneous at fibre speeds is what XSAN does and to do this you need it.
HTH,
=Tod
Intel Xserve, G5 XServes, XRAID, Promise

+The xserve raids will mount automatically to any computer that I connect the qlogic fc switch to+
This is source of the corruption to your data. Any computer that attaches to a drive/partition via fibre channel assumes that it alone is in control of the drive and data corruption is inevitable.
+Is that the issue, should I disconnect the xserve from the fc switch and leave it connected via ethernet?+
Short answer: YES. The ethernet connections are fine because the server is controlling the file arbitration through the sharing protocol. Fibre channel connections assumes complete control over the partition and no arbitration of the file access is performed. It's like two people independently driving trying to drive the same car to different locations.
Depending on your set-up it is possible for the two machines to see and use different parts of the Xserve RAID storage but they cannot access the same areas without SAN doing the arbitration.
Hope that's clear,
=Tod

Whole root zone and fibre channel hba

Similar Messages

Maybe you are looking for