Considerations When Planning For The Root Volume - IBM System Storage N Series Implementation Manual

Considerations when planning for the root volume

Root volume
defined
Options for the
location of the root
volume
24
Each gateway has a special volume called a root volume. The root volume is
required for the system to be able to boot and to function properly. The root
volume contains system files and configuration information. The root volume can
also contain data if you want it to. Core dump files, which are important for
troubleshooting, are written to the root volume if there is enough space.
On a gateway with native disks, the root volume can be on a disk shelf or on an
array LUN.
The benefits of the root volume on a native disk shelf are as follows:
◆
For a new gateway, initial setup and configuration is easier because you have
fewer steps to perform.
If you order a gateway with disk shelves, your system is delivered with the
root volume and with three disks—a RAID-DP aggregate with one parity
disk and two data disks. The root volume configured at the factory is a
FlexVol volume with a block checksum type.
◆
Greater availability of core dump files
When a native disk shelf is installed on a gateway and the root volume is
installed on a disk, core dumps are likely to be more available. If the root
volume is on an array LUN, a core file cannot be saved if the array LUN
becomes unavailable for some reason (for example, because of switch or
storage array issues). Installing the root volume on a native disk eliminates
the impact of network and network device failures on core file production.
Note
A core dump file is a valuable tool for technical support to use while
troubleshooting why a gateway crashed. When a gateway crashes, a core
dump file is saved to the root volume if adequate space is available on the
root volume.
Considerations when planning for the root volume