Disk and File System Management 3-7
The filer uses two naming conventions to indicate the root volume:
/vol/vol0
/
In the /vol/vol0 convention
/vol
Indicates that the next part of the path, such as vol0 in this example, is a volume
name.
/vol0
Indicates the default name of the root volume for a filer. You can change this
name using the vol rename command.
Mounting volumes: On filers configured with multiple volumes, mounting / is equiv-
alent to mounting /vol/vol0/, (where vol0 is the root directory of the root volume).
Paths that begin with / (for example, /etc) refer to directories on the root volume.
NOTE: /vol is not a directoryit is a special virtual root path under which the filer
mounts other directories. You cannot mount /vol to view all the volumes on the filer;
you must mount each filer volume separately.
In mount requests and server commands, prefix the path names of the volumes and
directories you want to mount using the convention /vol/volume_name/directory.
Example: For example, /vol/users/home/cheryl is a directory called /home/cheryl in a
volume named users.
'HWHUPLQLQJWKH1XPEHURI9ROXPHVWR8VH
Whether you should use the default single volume configuration or create additional
volumes depends mainly on the storage capacity of the filer.
Use of a single volume: If you want the filer to be configured with a single volume,
you do not need to do any further volume configuration after you complete the initial
setup.
If your filer doesnt have a large number of disks, a single-volume configuration is
probably all you need. You can create additional volumes in the future.
Use of multiple volumes: There are several factors to consider before deciding to
create and use multiple volumes:
Configuring with multiple volumes aids in the administration of filers that have large
storage capacities, enabling you to
Perform administrative and maintenance tasks, for example, backup and restore,
on individual volumes rather than on a single, large file system.
Set option command values, for example, snap sched, raidsize, minra,
no_atime_update, and so on, differently for individual volumes.