Sun Microsystems 10 Swap, Var/crash, Metadb, Zones/zone1, Zones/root, Zones/var, App1

Version 3.1-enSolaris 10 Container Guide - 3.1 5. Cookbooks Effective: 30/11/2009

5.1.3. Root disk layout

[dd]The following table gives an example for a root disk layout of a system with a local zone. The assumptions on the size of the file systems represent empirical values and examples and can vary depending on the scope of the software installation and local requirements.

Path		File system		Comment
		size
		(example)
/		8	GB	/opt for the global zone can be contained in this
swap		2	GB	depending on the size of the main memory, requirement and experience
				The dump device is also configured in the swap device.
/var		6	GB	depending on requirement and experience
/var/crash		4	GB	can	also	be located	within	/var	if	necessary
				Size depends on main memory size and experience
ABE	(/)	8	GB	Alternative boot environment (ABE) for /
ABE	(/var)	6 GB		ABE for /var
				/var/crash and swap can be shared among the two BE
metadb		100 MB		SVM meta database if the Solaris Volume Manager is used
/zones		2	GB	root file system for all zones, if several zones share a file system
/zones/zone1		1	GB	root file system exclusively for zone1
/zones/root		1	GB	root file system for several zones if several zones share a file system and if
				/var of the local zone is to be separate. Further partitioning e.g. into
				/zones/root/zone2, /zones/root/zone3, etc.
/zones/var		1	GB	/var file system for several zones if several zones are to share a file system but
				/var is separated and monitored separately. Further partitioning e.g. in
				/zones/var/zone2, /zones/var/zone3, etc.
/app1		1	GB	contains	the	application that	is to	run	within	the zone
				/app1 is e.g. mounted in the zone on /opt/app1, is separated from
				rootfs of the zone and can also be relocated independent of the zone.
Table 9: [dd] Root disk layout

Since Solaris 10 10/08, a root file system and the zone path can also be set up on ZFS. This allows ZFS file systems to be used for the individual file systems, and it is not necessary to provide a large number of slices and volumes. Care must be taken, however, that all file systems present within a zpool can only be moved/migrated/relocated to another system together. Therefore, if the plan is to migrate individual zones to other systems via zoneadm detach ... attach, these zones should have their own zpools assigned, or the file systems should be relocated via zfs send ...

receive.

68