Re: [zones-discuss] Zone installation problem.
That was kinda my thinking too but I guess an lofs mount would do the same thing. Quick question though, what is the major different between an inherit-pkg-dir and an lofs mount? This is one area of zones I haven't really researched that well. If you don't use inherit-pkg-dir, the zone installation will copy all packages installed in that directory. Not something you want for blastwave packages; you want to share them. Casper ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
Chris Greenman wrote: That was kinda my thinking too but I guess an lofs mount would do the same thing. Quick question though, what is the major different between an inherit-pkg-dir and an lofs mount? This is one area of zones I haven't really researched that well. There are several differences between inherit-pkg-dir and lofs mounts. * You can only set inherit-pkg-dir entries while configuring the zone. Once it is installed, they cannot be added or removed. This is not true for lofs mounts * An inherit-pkg-dir mount is read-only. Lofs mounts can be either read-only or read-write. * Probably the biggest one is that the inherit-pkg-dir settings are used to help figure out how pkgs are installed in the zone and what pkg data must be installed in the zone vs. inherited from the global zone. As a result, this also impacts zone migration dependency checking. This last point is fairly complex since there are no restrictions on what you can specify for inherit-pkg-dir but in reality, I don't think you could make arbitrary settings for those and have things always work. In general, we have the 4 standard values (/usr, /platform, /lib /sbin) for a sparse zone and no settings for a whole-root zone. The one gray area is probably /opt. We were just talking about this the other day and if we should impose some restrictions on inherit-pkg-dir to make things a little more sane. It might be helpful for us to hear from people what inherit-pkg-dir settings they use, beyond the standard sparse settings, and why they chose those. We are thinking about the possibility of having a setting for a sparse vs. whole-root zone instead of having to set inherit-pkg-dir, but we also recognize that there might be some issues around /opt. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
So am I right in assuming: inherit-pkg-dir = pkg install from global zone installs the files in the global zone and simply updates the package database in the non-global zone. and lofs = a package install from the global zone installs the files in the global zone then tries to install the files in the non-global zone (which fails of course because the file system is read only). --- [EMAIL PROTECTED] wrote: That was kinda my thinking too but I guess an lofs mount would do the same thing. Quick question though, what is the major different between an inherit-pkg-dir and an lofs mount? This is one area of zones I haven't really researched that well. If you don't use inherit-pkg-dir, the zone installation will copy all packages installed in that directory. Not something you want for blastwave packages; you want to share them. Casper Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
In general, we have the 4 standard values (/usr, /platform, /lib /sbin) for a sparse zone and no settings for a whole-root zone. The one gray area is probably /opt. We were just talking about this the other day and if we should impose some restrictions on inherit-pkg-dir to make things a little more sane. It might be helpful for us to hear from people what inherit-pkg-dir settings they use, beyond the standard sparse settings, and why they chose those. We are thinking about the possibility of having a setting for a sparse vs. whole-root zone instead of having to set inherit-pkg-dir, but we also recognize that there might be some issues around /opt. FWIW, I think this is a wise move; inherit-pkg-dir is a lot of rope. -- meem ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
Chris Greenman wrote: So am I right in assuming: inherit-pkg-dir = pkg install from global zone installs the files in the global zone and simply updates the package database in the non-global zone. inherit-pkg-dir assumes that the package is already installed in the global zone, and files from the pkg are in the directory specified with that directive. But yes, the zone's pkgs db is updated with about the pkgs in that directory. and lofs = a package install from the global zone installs the files in the global zone then tries to install the files in the non-global zone (which fails of course because the file system is read only). Using a lofs mount does not cause any pkg-related actions. It's simply another fs mount type. If you lofs-mount a directory into a zone, and the dir has pkgs installed into it, users in the zone should be able to use the application installed by the pkg, but would not be able to use pkginfo or pkgchk to determine that the pkg has been installed. Further, if you want to patch the pkg later, the patch tools will decide that the pkg is not installed in the zone and refuse to patch that zone. --- [EMAIL PROTECTED] wrote: That was kinda my thinking too but I guess an lofs mount would do the same thing. Quick question though, what is the major different between an inherit-pkg-dir and an lofs mount? This is one area of zones I haven't really researched that well. If you don't use inherit-pkg-dir, the zone installation will copy all packages installed in that directory. Not something you want for blastwave packages; you want to share them. Casper Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ___ zones-discuss mailing list zones-discuss@opensolaris.org -- -- Jeff VICTOR Sun Microsystemsjeff.victor @ sun.com OS AmbassadorSr. Technical Specialist Solaris 10 Zones FAQ:http://www.opensolaris.org/os/community/zones/faq -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
Chris Greenman wrote: Hello, I've got a problem I hope someone can help me with. I have two identical E250s (both jumpstarted identically) and I'm having problems installing a zone on one of them. The problem appears to center around some loopback filesystems I'm trying to create. The config file works fine on one machine but not the other. I've even gone as far as making an exact copy of the loopback directories on the working system and transferred them to the other with no luck. My zonecfg config file is as follows: create -b set zonepath=/zones/mysql1 set autoboot=true add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform end add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end add inherit-pkg-dir set dir=/usr/sfw end add inherit-pkg-dir set dir=/opt/csw end add fs set dir=/opt/csw/etc set special=/zones/local/mysql1/optcswetc set type=lofs add options [rw,nodevices] end add fs set dir=/opt/csw/var set special=/zones/local/mysql1/optcswvar set type=lofs add options [rw,nodevices] end add fs set dir=/usr/local set special=/zones/local/mysql1/usrlocal set type=lofs add options [rw,nodevices] end add net set address=192.168.0.70 set physical=hme0 end On system 1 this works fine. On system 2, I get the following error: # zonecfg -z mysql1 -f /var/tmp/mysql1-zone.cfg # zoneadm -z mysql1 install Preparing to install zone mysql1. ERROR: Read-only file system: cannot create mount point /zones/mysql1/root/opt/csw/var ERROR: Read-only file system: cannot create mount point /zones/mysql1/root/usr/local ERROR: cannot setup zone mysql1 inherited and configured file systems ERROR: cannot setup zone mysql1 file systems inherited and configured from the global zone ERROR: cannot create zone boot environment mysql1 zoneadm: zone 'mysql1': '/usr/lib/lu/lucreatezone' failed with exit code 74. # Notice the first FS works but the other 2 fail. Here is an ls of the loopback dirs in the global zone. # ls -l /zones/local/ total 2 drwxr-xr-x 5 root root 512 Dec 5 13:07 mysql1 # ls -l /zones/local/mysql1 total 6 drwxr-xr-x 2 root root 512 Dec 5 13:07 optcswetc drwxr-xr-x 2 root root 512 Dec 5 13:07 optcswvar drwxr-xr-x 2 root root 512 Dec 5 13:07 usrlocal Anyone have any suggestions? Because the directory /opt/csw is configured as an inherited-pkg-dir, it will be mounted read-only in the zone. It looks like the mount point for the lofs mounts, starting with /opt/csw/var, might not exist. Have you verified that there is actually an /opt/csw/var directory in /opt/csw in the global zone? Likewise for the /usr/local lofs mount. Why are you using inherited-pkg-dirs for some of the /opt subdirectories? Is there a reason you don't want to just use lofs mounts for those too? Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
On 12/6/06, Jerry Jelinek [EMAIL PROTECTED] wrote: lofs mount. Why are you using inherited-pkg-dirs for some of the /opt subdirectories? Is there a reason you don't want to just use lofs mounts for those too? In my environment, I have made inherited /opt by default for all new zones created. This has caused problems here and there when zones need to install software in /opt (or mount existing NFS/SAN file systems there). The workaround has been one of the following: 1) Create the mount point in the global zone (yuck) 2) Rebuild the zone without inherited /opt (yuck) As I look forward to possibly including blastwave in standard images, I am thinking that Chris' approach of inherit-pkg-dir of /opt/csw (and any other kinda big directories in /opt) is the more proper way to go. Mike -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
Sorry for not posting back to the list. Yes indeed, this was the problem. /opt/csw/var and /usr/local did NOT exist in the global zone. Thanks to James Carlson for first pointing this out. Have you verified that there is actually an /opt/csw/var directory in /opt/csw in the global zone? Likewise for the /usr/local lofs mount. Why are you using inherited-pkg-dirs for some of the /opt subdirectories? Is there a reason you don't want to just use lofs mounts for those too? Jerry Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Zone installation problem.
Chris Greenman writes: add inherit-pkg-dir set dir=/usr/sfw end Why would /usr/sfw be a separate mount point? ERROR: Read-only file system: cannot create mount point /zones/mysql1/root/opt/csw/var At a guess, this occurs because /zones/mysql1 itself is mounted read-only. Can you check how that file system is mounted? -- James Carlson, KISS Network[EMAIL PROTECTED] Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ zones-discuss mailing list zones-discuss@opensolaris.org
