Hello,

We are building zones over veritas volumes, I have been able to liveupgrade
systems with zones, but I'm  now trying to reduce the
downtime, liveupgrade doesn't seem to like using /dev/vx devices, therefore
I tried various ways, the working one was to create
a new /zones filesystem using a striped md device ... but then the operation
to move back all the whole root disks (/ and /var) back onto
veritas devices is long.
I decided to try another way using temporary md devices with the hope to
then simply ufsdump the / and /var md devices into the original
volume group ... but visibly liveupgrade requires the / from all zones to be
bootable ??? Why does it care ?

vsmd9002:/ #cat lucreate.sh
lucreate -n u4 -C /dev/dsk/c1t0d0s0 -m /:/dev/dsk/c1t0d0s3:ufs:global -m
/var:/dev/dsk/c1t0d0s4:ufs:global -m /var:/dev/md/dsk/d102:ufs:dbsz9002 -m
/:/dev/md/dsk/d101:ufs:dbsz9002 -m /:/dev/md/dsk/d103:ufs:dbsz9003 -m
/var:/dev/md/dsk/d104:ufs:dbsz9003 -m /:/dev/md/dsk/d105:ufs:dbsz9004 -m
/var:/dev/md/dsk/d106:ufs:dbsz9004 -m /:/dev/md/dsk/d107:ufs:dbsz9005 -m
/var:/dev/md/dsk/d108:ufs:dbsz9005
vsmd9002:/ #sh lucreate.sh
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <d30> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Searching /dev for possible boot environment filesystem devices

ERROR: Cannot determine boot device for metadevice </dev/md/dsk/d107>.
ERROR: Cannot determine boot device for Solaris Volume Manager metadevice
</dev/md/dsk/d107>. The only metadevices that support the root file system
are a stripe with only a single disk or a mirror on a single-disk stripe.

For the fun of it, I tried the same but moving /usr to the md devices and
there it worked...


Analyzing system configuration.
Comparing source boot environment <d30> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Searching /dev for possible boot environment filesystem devices

Updating system configuration files.
The device </dev/dsk/c1t0d0s3> is not a root device for any boot
environment; cannot get BE ID.
Creating configuration for boot environment <u4>.
Source boot environment is <d30>.
Creating boot environment <u4>.
Creating file systems on boot environment <u4>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c1t0d0s3>.
Creating <ufs> file system for </var> in zone <global> on
</dev/dsk/c1t0d0s4>.
Creating <ufs> file system for </usr> in zone <dbsz9002> on
</dev/md/dsk/d101>.
Creating <ufs> file system for </var> in zone <dbsz9002> on
</dev/md/dsk/d102>.
Creating <ufs> file system for </usr> in zone <dbsz9003> on
</dev/md/dsk/d103>.
Creating <ufs> file system for </var> in zone <dbsz9003> on
</dev/md/dsk/d104>.
Creating <ufs> file system for </usr> in zone <dbsz9004> on
</dev/md/dsk/d105>.
Creating <ufs> file system for </var> in zone <dbsz9004> on
</dev/md/dsk/d106>.
Creating <ufs> file system for </usr> in zone <dbsz9005> on
</dev/md/dsk/d107>.
Creating <ufs> file system for </var> in zone <dbsz9005> on
</dev/md/dsk/d108>.
Mounting file systems for boot environment <u4>.
Calculating required sizes of file systems for boot environment <u4>.
Populating file systems on boot environment <u4>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Populating contents of mount point </var>.
Populating contents of mount point </usr>.
Populating contents of mount point </var>.
Populating contents of mount point </usr>.
Populating contents of mount point </var>.
Populating contents of mount point </usr>.
Populating contents of mount point </var>.
Populating contents of mount point </usr>.
Populating contents of mount point </var>.
Copying.
Creating shared file system mount points.
Copying root of zone <dbsz9002>.
Copying </usr> in zone <dbsz9002>.
Copying </var> in zone <dbsz9002>.
cpio: "run/.inetd.uds" ?
1 error(s)
WARNING: Zone <dbsz9002> mount point </var>: data copy incomplete
        See </tmp/.lucopy.cpio_err.13598.dbsz9002.d102> for details.
Copying root of zone <dbsz9003>.
Copying </usr> in zone <dbsz9003>.
Copying </var> in zone <dbsz9003>.
cpio: "run/.inetd.uds" ?
1 error(s)
WARNING: Zone <dbsz9003> mount point </var>: data copy incomplete
        See </tmp/.lucopy.cpio_err.13598.dbsz9003.d104> for details.
Copying root of zone <dbsz9004>.
ERROR: Zone <dbsz9004> in BE <d30>: cannot copy root
        See </tmp/.lucopy.cpio_err.13598.dbsz9004> for details.
Copying root of zone <dbsz9005>.
ERROR: Zone <dbsz9005> in BE <d30>: cannot copy root
        See </tmp/.lucopy.cpio_err.13598.dbsz9005> for details.
Creating compare databases for boot environment <u4>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <u4>.
Making boot environment <u4> bootable.
Setting root slice to </dev/dsk/c1t0d0s3>.
Population of boot environment <u4> successful.
Creation of boot environment <u4> successful.

Regards

-- 
Gael Martinez
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to