Root Disk Layout - Sun Microsystems SOLARIS 10 Manual

Version 3.1-en
Solaris 10 Container Guide - 3.1 5. Cookbooks

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
/
sw ap
/v ar
/v ar/ cr ash
AB E ( /)
AB E ( /v ar)
me tad b
/z one s
/z one s/ zon e 1
/z one s/ roo t
/z one s/ var
/a pp1
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 zo ne a dm de t ac h .. . a t ta ch , these zones
should have their own zpools assigned, or the file systems should be relocated via z f s se n d .. .
r ec eiv e.
File system Comment
size
(example)
8 GB / o p t
2 GB depending on the size of the main memory, requirement and experience
The dump device is also configured in the swap device.
6 GB depending on requirement and experience
4 GB
can also
Size depends on main memory size and experience
8 GB
Alternative boot environment (ABE) for
6 GB v a r
ABE for /
/ v a r / c ra sh
100 MB SVM meta database if the Solaris Volume Manager is used
2 GB root file system for all zones, if several zones share a file system
1 GB root file system exclusively for zone1
1 GB root file system for several zones if several zones share a file system and if
/ v a r
/zones/root/zone2, /zones/root/zone3, etc.
1 GB /var file system for several zones if several zones are to share a file system but
/ v a r
is separated and monitored separately. Further partitioning e.g. in
/ z o n e s /v ar / zo ne 2
1 GB contains
/ a p p 1
rootfs of the zone and can also be relocated independent of the zone.
for the global zone can be contained in this
be located
sw ap
and can be shared among the two BE
of the local zone is to be separate. Further partitioning e.g. into
/ z on es / va r/ z on e3
,
the application that
is e.g. mounted in the zone on
Effective: 30/11/2009
/ va r
within if
/
, etc.
is to run within
/o p t/ ap p 1
, is separated from
necessary
the zone
68