[zfs-discuss] Re: [zones-discuss] Zones on large ZFS filesystems
Niclas Sodergard wrote: Hi everyone, Sorry for crossposting but it seems I have stumbled upon a problem that affects both. I have a V490 running Solaris 10u3 with a 16x750GB raid array connected to it. I've created an 8TB zfs filesystem called data1 and created a zfs filesystem called data1/zones mounted to /zones. The structure looks like this ... When I execute zoneadm -z mytest install I get the following error: # zoneadm -z mytest install zoneadm: /zones/mytest: Value too large for defined data type could not verify zonepath /zones/mytest because of the above errors. zoneadm: zone mytest failed to verify While this doesn't help with your immediate issue, this is a known bug: 6433526 zoneadm should use statvfs64 It was fixed in opensolaris in b44 and it is also fixed in S10u4, although that is not available yet. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zones-discuss] Re: [zfs-discuss] Downsides to zone roots on ZFS?
Ivan Buetler wrote: Jerry, Thank you for your response. See my zonecfg of the named NGZ here: [EMAIL PROTECTED] ~ # zonecfg -z named export create -b set zonepath=/zpool/zones/named 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 fs set dir=/zpool/applic/bind-9.3.2-P1 set special=/zpool/applic/bind-9.3.2-P1/ set type=lofs add options ro add options nodevices end add fs set dir=/zpool/data/named set special=/zpool/data/named set type=lofs add options rw add options nodevices end add net set address=1.2.3.4/27 set physical=qfe3 end add net set address=21.2.3.5/27 set physical=qfe3 end add net set address=10.10.10.10/24 set physical=qfe4 end add attr set name=comment set type=string set value="Zone named" end It looks like you won't be able to upgrade. Assuming /zpool is the mount of your zfs zpool, then your zonepath is on a zfs dataset so this is the exact issue that upgrade cannot handle yet. If you were to place your zones on a UFS filesystem then the other fs entries you have to mount zfs datasets within the zone would be fine. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zones-discuss] Re: [zfs-discuss] Downsides to zone roots on ZFS?
Ivan Buetler wrote: Is this true for OpenSolaris? My experience: I was trying to upgrade from "SunOS 5.11 snv_28" to "SunOS 5.11 snv_54" where my NGZ zone roots were set to a zfs mount point like below: NAME USED AVAIL REFER MOUNTPOINT zpool 93.8G 40.1G26K /zpool zpool/zones 3.50G 40.1G 1.68G /zpool/zones Upgrading to SNV_54 did not work for me (CD|DVD|Live-Upgrade). The install procedure was cancelled after it came to the NGZ ZFS setup part. However - I was enforced to to a full re-install of the whole OS. By this time, I decided to have an OS independent application setup: I decided to leave all my Non-Solaris apps within the following structure: NAME USED AVAIL REFER MOUNTPOINT zpool 93.8G 40.1G26K /zpool zpool/applic2.40G 40.1G 2.40G /zpool/applic zpool/bin108M 40.1G 108M /zpool/bin zpool/data 644M 40.1G 644M /zpool/data zpool/logs 1.03G 40.1G 1.03G /zpool/logs This means, Apache, Tomcat, Bind DNS, Postfix, MySQL, Berkeley-DB, ... was installed using a prefix (e.g. ./configure --prefix=/zpool/applic/named) This gives me some independencies to the core OS located in /sbin; /usr/bin, ... After I moved all my apps into my own prefix path (ZFS mount poing), I did another full reinstall of the OS, where I found out that I should have backed up some files from the core OS before. Especially I should have backed up the following files from the GZ and all NGZ. a) /etc/hosts, /etc/passwd, /etc/shadow, /etc/nsswitch.conf, /etc/resolv.conf b) /etc/hostname.XX, c) /etc/init.d/startup-scripts (my own releases) After I did another full setup (not upgrading), I created the zones using the famous zonemgr script and brought back all applications by just mounting the /zpool/applic/path into the NGZ path. This way, I was pretty fast in upgrading the whole system to a new Nevada build, even upgrading would be the preferred solution to me. I do not know if I with SNV_54, another upgrade from SNV_54 to SNV_55 is supported by OpenSolaris. That is why this thread is of interest to me. Ivan, I am not sure if I completely understand your configuration, but you can upgrade a system with zones that have delegated zfs datasets or where you just used lofs mounts to mount the zfs filesystems into the zone. This would apply when all you have is data or non-Solaris pkgs installed in the zfs filesystems. Since the upgrade code does not have to discover and mount the zfs filesystems to perform the upgrade of the OS, this type of configuration works fine. We would have to see your actual zonecfg info to be sure that you haven't set things up in a way that would prevent the upgrade though. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Downsides to zone roots on ZFS?
Rich Teer wrote: Excellent; disk space won't be an issue for me, nor will the non-live-upgradability, so I'll be putting my zone roots on ZFS. Rich, Just to be clear, both live-upgrade and the mini-root upgrade do not yet know about zfs so if you place your zones on zfs, you won't be able to do either style of upgrade until that is fixed. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zones-discuss] Re: [zfs-discuss] Downsides to zone roots on ZFS?
John Clingan wrote: This is incorrect. All S10 updates have supported upgrading systems with zones. I believe what you are thinking of is that live-upgrade does not support upgrading systems with zones. This is being fixed in the next S10 update. It is already fixed in nevada. Which Nevada build? The install code changes look like they were integrated into b53. Some of the zones support that was needed had been integrated earlier. The bug is 6264796. When will zone roots on ZFS be supported by live upgrade? I don't know. Asking the install team would be your best bet. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Downsides to zone roots on ZFS?
Rich, Rich Teer wrote: Hi all, Last time I checked, having one's zone roots (zonepaths) on ZFS file systems was not a recommended practice, despite the fact that this works. IIRC, the problem was that the upgrade code didn't grok zfs and would therefore get terribly confused should the zone roots reside on ZFS. However, given that S10 11/06 doesn't support upgrading of zones anyway (even if they reside on UFS file systems), is this point moot? (Or is that applicable to live upgrade only?) This is incorrect. All S10 updates have supported upgrading systems with zones. I believe what you are thinking of is that live-upgrade does not support upgrading systems with zones. This is being fixed in the next S10 update. It is already fixed in nevada. More succinctly: apart from not being able to upgrade (presumably an initial reinstall will be required), what are the reasons for NOT hosting zone roots on ZFS? That is the only real reason. The only other reason I know of is fairly obscure. The patch tools don't know about zfs so they can miscalculate space when you have a set of zones, each on their own zfs dataset, but in the same zpool. If you were really tight on space, the patch process might fail partway through as a result. This is probably not an issue for most people but is the only other one I know of. Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Zones root-fs in ZFS ? (fwd)
Eric Schrock wrote: Upon closer inspection, we found that this scenario should work with the current upgrade solution. What will definitely not work is to delegate a ZFS dataset to a local zone, and then place system software (i.e. Solaris package contents) within such a filesystem. This should work if the mountpoint is set to 'legacy', however. Actually, if you try that, I think this bug will break you when you try to patch or upgrade. 6412875 zoneadm mount does not mount filesystems in vfstab Jerry ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
