Nas File Systems; Table 68 System Volumes - Fujitsu ETERNUS DX S5 Series Design Manual

4. NAS Functions
NAS System (NAS Volume Management)

NAS File Systems

When the first NAS Thin Provisioning Volume (TPV) is created in the ETERNUS DX, system volumes ($SYSVOL1,
$SYSVOL2, and $SYSVOL3) are automatically created in the same pool where the TPV is created and then the
NAS file system is created.
A NAS file system can be used as a shared folder with Windows or UNIX/Linux. For VMware, the NAS file system
can be used as a data store to store data such as configuration information and the OS of the virtual machine.
IMPORTANT
During the configuration phase
• The time it takes to create a file system (NAS volume) varies depending on whether system volumes
exist. If system volumes do not exist within the ETERNUS DX, creating a file system takes 10 to 15
minutes longer than usual because system volumes are created while creating the file system.
Processing takes up to 30 minutes.
• The total capacity of the NAS user volumes, NAS backup volumes, and the system volumes (25GB) must
not exceed the maximum pool capacity. TPVs and FTVs for a SAN connection are also included.
For more details about the maximum pool capacity setting, refer to "Set Thin Provisioning" in "ETERNUS
Web GUI User's Guide".
During the operation phase
The procedure to delete all the system volumes is as follows.
1
Delete all the NAS volumes.
2
Delete all the expanded system volumes.
3
Delete all the system volumes.
When the system volumes are deleted, the NAS system reboots. When performing a NAS configuration
after deleting the system volume, check whether the reboot is complete and the status of the NAS Engine
is "Maintenance/0xE000" using ETERNUS CLI.
Deleting all system volumes ($SYSVOL1, $SYSVOL2, and $SYSVOL3) at once is recommended. When system
volumes are deleted one by one, delete the next system volume after the system is rebooted.
■
System Volumes
A system volume consists of three volumes that has a total capacity of 25GB. Two of the three system volumes
are for the Rootfs partition for each controller. The remaining volume is for the file system management
partition.
System volume names cannot be changed.
The following table shows the name, capacity, and usage of the system volumes.
Table 68 System Volumes
Volume name
$SYSVOL1
$SYSVOL2
$SYSVOL3
Capacity Usage
1GB File system management partition
12GB Rootfs partition for CM#0
12GB Rootfs partition for CM#1
164 Design Guide