Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

List the component volumes of the previously created volume set:

# vxvset -g dg1 list myvset

VOLUME INDEX LENGTH STATE CONTEXT

vol1 0 20480 ACTIVE -

vol2 1 102400 ACTIVE -

vol3 2 102400 ACTIVE -

Use the ls command to see that when a volume set is created, the volumes

contained by the volume set are removed from the namespace and are instead

accessed through the volume set name:

# ls -l /dev/vx/rdsk/rootdg/myvset

crw------- 1 root root 108,70009 May 21 15:37

/dev/vx/rdsk/rootdg/myvset

Create a volume, add it to the volume set, and use the ls command to see that

when a volume is added to the volume set, it is no longer visible in the

namespace:

# vxassist -g dg1 make vol4 50m

# ls -l /dev/vx/rdsk/rootdg/vol4

crw------- 1 root root 108,70012 May 21 15:43

/dev/vx/rdsk/rootdg/vol4

# vxvset -g dg1 addvol myvset vol4

# ls -l /dev/vx/rdsk/rootdg/vol4

/dev/vx/rdsk/rootdg/vol4: No such file or directory

Creating multi-volume file systems

When a multi-volume file system is created, all volumes are dataonly, except

volume zero, which is used to store the file system's metadata. The volume

availability flag of volume zero cannot be set to dataonly.

As metadata cannot be allocated from dataonly volumes, enough metadata space

should be allocated using metadataok volumes. The "file system out of space"

error occurs if there is insufficient metadata space available, even if the df

command shows that there is free space in the file system. The fsvoladm command

can be used to see the free space in each volume and set the availability flag of

the volume.

Unless otherwise specified, VxFS commands function the same on multi-volume

file systems as the commands do on single-volume file systems.

93Multi-volume file systems

Creating multi-volume file systems