Overview of Volumes

A volume is a group of physical slices that appears to the system as a single, logical device. Volumes are actually pseudo, or virtual, devices in standard UNIX® terms.

Historically, the Solstice DiskSuite^TM product referred to these logical devices as metadevices. However, for simplicity and standardization, this book refers to these devices as volumes.

Classes of Volumes

You create a volume as a RAID-0 (concatenation or stripe) volume, a RAID-1 (mirror) volume, a RAID-5 volume, .

You can use either the Enhanced Storage tool within the Solaris Management Console or the command-line utilities to create and administer volumes.

The following table summarizes the classes of volumes.

How Volumes Are Used

You use volumes to increase storage capacity, performance, and data availability. In some instances, volumes can also increase I/O performance. Functionally, volumes behave the same way as slices. Because volumes look like slices, the volumes are transparent to end users, applications, and file systems. As with physical devices, volumes are accessed through block or raw device names. The volume name changes, depending on whether the block or raw device is used. See Volume Names for details about volume names.

You can use most file system commands, including mkfs, mount, umount, ufsdump, ufsrestore, and others, on volumes. You cannot use the format command, however. You can read, write, and copy files to and from a volume, as long as the volume contains a mounted file system.

Example—Volume That Consists of Two Slices

Figure 3–2 shows a volume that contains two slices, one slice from Disk A and one slice from Disk B. An application or UFS treats the volume as if it were one physical disk. Adding more slices to the volume increases its storage capacity.

Figure 3–2 Relationship Among a Volume, Physical Disks, and Slices

Volume and Disk Space Expansion Using the growfs Command

Solaris Volume Manager enables you to expand a volume by adding additional slices. You can use either the Enhanced Storage tool within the Solaris Management Console or the command-line interface to add a slice to an existing volume.

You can expand a mounted or unmounted UFS file system that is contained within a volume without having to halt or back up your system. Nevertheless, backing up your data is always a good idea. After you expand the volume, use the growfs command to grow the file system.

After a file system has been expanded, the file system cannot be reduced in size. The inability to reduce the size of a file system is a UFS limitation. Similarly, after a Solaris Volume Manager partition has been increased in size, it cannot be reduced.

Applications and databases that use the raw volume must have their own method to “grow” the added space so that applications can recognize it. Solaris Volume Manager does not provide this capability.

You can expand the disk space in volumes in the following ways:

• Adding one or more slices to a RAID-0 volume

• Adding one or more slices to all submirrors of a RAID-1 volume

• Adding one or more slices to a RAID-5 volume

• Expanding a soft partition with additional space from the underlying component

The growfs command expands a UFS file system without loss of service or data. However, write access to the volume is suspended while the growfs command is running. You can expand the file system to the size of the slice or the volume that contains the file system.

The file system can be expanded to use only part of the additional disk space by using the -s size option to the growfs command.

When you expand a mirror, space is added to the mirror's underlying submirrors. The growfs command is then run on the RAID-1 volume. The general rule is that space is added to the underlying devices, and the growfs command is run on the top-level device.

Volume Names

As with physical slices, volumes have logical names that appear in the file system. Logical volume names have entries in the /dev/md/dsk directory for block devices and the /dev/md/rdsk directory for raw devices. Instead of specifying the full volume name, such as /dev/md/dsk/volume-name, you can often use an abbreviated volume name, such as d1, with any meta* command. You can generally rename a volume, as long as the volume is not currently being used and the new name is not being used by another volume. For more information, see Exchanging Volume Names.

Originally, volume names had to begin with the letter “d” followed by a number (for example, d0). This format is still acceptable. The following are examples of volume names that use the “d*” naming construct:

/dev/md/dsk/d0

Block volume d0

/dev/md/dsk/d1

Block volume d1

/dev/md/rdsk/d126

Raw volume d126

/dev/md/rdsk/d127

Raw volume d127

Beginning with the Solaris Express 4/06 release, Solaris Volume Manager has been enhanced to include the use of descriptive names for naming volumes and hot spare pools. A descriptive name for a volume is a name that can be composed of a combination of the following:

• Alphanumeric characters

• “-” (a dash)

• “_” (an underscore)

• “.” (a period)

Descriptive names must begin with a letter. The words “all” and “none” are reserved and cannot be used as names for volumes or hot spare pools. You also cannot use only a “.” (period) or “..” (two periods) as the entire name. Finally, you cannot create a descriptive name that looks like a physical disk name, such as c0t0d0s0. As noted previously, you can also continue to use the “d*” naming convention. The following are examples of descriptive volume names:

When descriptive names are used in disk sets, each descriptive name must be unique within that disk set. Hot spare pools and volumes within the same disk set cannot have the same name. However, you can reuse names within different disk sets. For example, if you have two disk sets, one disk set called admins and one disk set called managers, you can create a volume named employee_files in each disk set.

The functionality of the Solaris Volume Manager commands that are used to administer volumes with descriptive names remains unchanged. You can substitute a descriptive name in any meta* command where you previously used the “d*” format. For example, to create a single-stripe volume of one slice with the name employee_files, you would type the following command at the command line:

# metainit employee_files 1 1 c0t1d0s4

If you create volumes and hot spare pools using descriptive names and then later determine that you need to use Solaris Volume Manager under previous releases of the Solaris OS, you must remove the components that are defined with descriptive names. To determine if the Solaris Volume Manager configuration on your system contains descriptive names, you can use the -D option of the metastat command. The metastat -D command lists volumes and hot spare pools that were created using descriptive names. These components must be removed from the Solaris Volume Manager configuration before the remaining configuration can be used with a release prior to the Solaris Express 4/06 release. If these components are not removed, the Solaris Volume Manager in these prior Solaris releases does not start. For more information about the -D option, see the metastat(1M) man page. For information about removing components from a configuration, see Removing RAID-1 Volumes (Unmirroring) and Removing a RAID-0 Volume.

Volume Name Guidelines

The use of a standard for your volume names can simplify administration and enable you at a glance to identify the volume type. Here are a few suggestions:

• Use ranges for each type of volume. For example, assign numbers 0–20 for RAID-1 volumes, 21–40 for RAID-0 volumes, and so on.

• Use a naming relationship for mirrors. For example, name mirrors with a number that ends in zero (0), and submirrors that end in one (1), two (2), and so on. For example, you might name mirrors as follows: mirror d10, submirrors d11 and d12; mirror d20, submirrors d21, d22, d23, and d24. In an example using descriptive names, you could use a naming relationship such as employee_mirror1 for a mirror with employee_sub1 and employee_sub2 comprising the submirrors.

• Use a naming method that maps the slice number and disk number to volume numbers.