Table of Contents
Advertisement
Reference Letter
Explanation
The NSS file system logically combines multiple partitions to form pools of space (up
G
to 8 TB in size) that can span multiple devices.
In the illustration, POOL_LX contains two NSS partitions that are created from the
unformatted space on both hard disks when the pool is created.
In some ways, NSS pools are like pools of water. The space from each partition is
logically "poured" into an NSS pool and made available to the pool's assigned
volumes, such as HOME_NSS. Neither the volume nor the users with rights to
access it know which physical partitions contain the disk space actually being used.
Of course, the NSS file system continues to track each partition below the surface,
but from a logical standpoint, all of the disk space assigned to a pool is one
continuous source of disk space.
The sole purpose of NSS pools is to provide storage space from which you can form
H
one or more NSS volumes.
Your lab server contains a single NSS pool named POOL_LX with a single NSS
volume named HOME_NSS. The pool's free space is unallocated until used.
The instructions for creating the HOME_NSS volume leave the option set to have
I
the volume grow to the pool size. As additional space is needed, the HOME_NSS
volume automatically expands into the free space shown.
Free space in the pool is not reserved for the HOME_NSS volume; instead, space is
J
allocated to HOME_NSS as needed. You can optionally add other volumes to the
same pool and, in a sense, "overbook" the pool's free space.
You can also grow the pool as needed by adding more NSS partitions to the pool.
K
A.2 iManager Tomcat Error
If you experience a Tomcat error when attempting to access iManager 2.7, the likely cause is a
corrupted browser cookie. Clearing the browser cookies should solve the problem.
1 In Firefox, click Tools > Clear Private Data.
2 Select Cookies.
3 Deselect the other options.
4 Click Clear Private Data Now.
Supplementary Information 109
Advertisement
Chapters
Table of Contents
