Re: [zones-discuss] PS Re: Fwd: Live Upgrade and sparse root zones with their own /usr?
On Mon, May 11, 2009 at 7:50 AM, James Carlson james.d.carl...@sun.com wrote: Ouch. The man page for zonecfg(1M) says: A sparse zone inherits the following directories: /lib /platform /sbin /bin Although zonecfg allows you to remove one of these as an inherited directory, you should not do so. You should either follow the whole-root model or the sparse model; a subset of the sparse model is not tested and you might encounter unex- pected problems. I don't see /usr in that list. However, I've built a test machine and when I try to do a live upgrade I get this error: # luupgrade -n secondary -u -s /cdrom/cdrom0 42092 blocks miniroot filesystem is lofs Mounting miniroot at /cdrom/cdrom0/Solaris_10/Tools/Boot Validating the contents of the media /cdrom/cdrom0. The media is a standard Solaris media. The media contains an operating system upgrade image. The media contains Solaris version 10. Constructing upgrade profile to use. Locating the operating system upgrade program. Checking for existence of previously scheduled Live Upgrade requests. Creating upgrade profile for BE secondary. Determining packages to install or upgrade for BE secondary. Performing the operating system upgrade of the BE secondary. CAUTION: Interrupting this process may leave the boot environment unstable or unbootable. ERROR: Installation of the packages from this media of the media failed; pfinstall returned these diagnostics: Processing profile ERROR: This slice can't be upgraded because of missing usr packages for the following zones: ERROR:testzone ERROR:testzone ERROR: This slice cannot be upgraded because of missing usr packages for one or more zones. The Solaris upgrade of the boot environment secondary failed. # ls /space/testzone -- Am I just hosed? Do I need to rebuild my machines with whole-root zones? That's gonna eat up some space. ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] PS Re: Fwd: Live Upgrade and sparse root zones with their own /usr?
Elizabeth Schwartz writes: Although zonecfg allows you to remove one of these as an inherited directory, you should not do so. You should either follow the whole-root model or the sparse model; a subset of the sparse model is not tested and you might encounter unex- pected problems. I don't see /usr in that list. Good point. However the original issue about using a subset of the sparse stands. It's never tested and unlikely to work right. Am I just hosed? Do I need to rebuild my machines with whole-root zones? That's gonna eat up some space. If you need whole-root, then that's what you'll need to do. You may want to check out the ZFS clone features, as that'll save a significant amount of space. In some cases, you don't actually need whole-root. All you really need are some writable directories inside the inherited mount points. In those cases, you can set up lofs mounts to provide writable storage to the zone. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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
Re: [zones-discuss] PS Re: Fwd: Live Upgrade and sparse root zones with their own /usr?
Mutter. Thanks for the fast response. It'd be nice if it had some sort of *warning* if it isn't safe, I certainly found a lot of sites suggesting that particular modification (removing /usr as an inherited dir). I'm building zones that run apache servers (mostly, coolstack) and the web folks have all sorts of stuff that wants to write into /usr, not /usr/local, at least out of the can. And there didn't seem to be any particular reason NOT to do this, so we've been up and running for over a year in this configuration. Oh well, at least I've gotten pretty good at rebuilding apache zones quick from scratch...I'll give the detached upgrade a whirl but if it doesn't work I'll rebuild as whole root. I'm feeling kinda crabby about this because I usually try so very hard to stay with vanilla, standard, supported configurations, everything in its place in case I get hit by a bus. Removing /usr from the set just didn't feel like it was going to be a big problem... thanks again Betsy ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] PS Re: Fwd: Live Upgrade and sparse root zones with their own /usr?
Elizabeth Schwartz writes: PS was creating sparse zones with their own /usr directories a totally dumb idea? At the time we did it because we had apache stuff that was trying to poke into /usr and I wanted to allow the web developers to play with /usr if needed. But I'm worried that I've broken the model as far as getting this all to work. Ouch. The man page for zonecfg(1M) says: A sparse zone inherits the following directories: /lib /platform /sbin /bin Although zonecfg allows you to remove one of these as an inherited directory, you should not do so. You should either follow the whole-root model or the sparse model; a subset of the sparse model is not tested and you might encounter unex- pected problems. Basically, the two models that are fully tested and supported are sparse root and whole root. Sparse root inherits all of the directories as listed above. Whole root inherits none of them. You can augment those models by adding new things to inherit with a sparse root and by doing overlay mounts of directories that do *not* include packaged software (e.g., /usr/local can be made writable), but removing just some of the things on the sparse list will likely run you into upgrade trouble. -- James Carlson, Solaris Networking james.d.carl...@sun.com Sun Microsystems / 35 Network Drive71.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
[zones-discuss] PS Re: Fwd: Live Upgrade and sparse root zones with their own /usr?
PS was creating sparse zones with their own /usr directories a totally dumb idea? At the time we did it because we had apache stuff that was trying to poke into /usr and I wanted to allow the web developers to play with /usr if needed. But I'm worried that I've broken the model as far as getting this all to work. ___ zones-discuss mailing list zones-discuss@opensolaris.org
