px, where x is the number of the plex in the volume. No name is necessary as the system automatically generates a name from the volume name by adding the suffix. The only required parameter is the organization, in this case concat. The only required attribute is the name, in this case myvol. This separation of symbolic names from device names allows disks to be moved from one location to another without confusion. The drive line describes a disk partition ( drive) and its location relative to the underlying hardware. With the exception of a small area at the beginning of the drive, which is used for storing configuration and state information, the entire drive is available for data storage. vinum drives can contain any number of subdisks. Subdisks reside on vinum drives, currently UNIX® partitions. Instead, vinum subdivides a single UNIX® partition, the drive, into contiguous areas called subdisks, which are used as building blocks for plexes. In fact, this turns out to be too inflexible as UNIX® disks can have only a limited number of partitions. Since vinum exists within the UNIX® disk storage framework, it would be possible to use UNIX® partitions as the building block for multi-disk plexes. Think of plexes as individual disks in a mirrored array, each containing the same data. This level in the hierarchy provides redundancy. Volumes are composed of plexes, each of which represent the total address space of a volume. Volumes have essentially the same properties as a UNIX® disk drive, though there are some minor differences. The most visible object is the virtual disk, called a volume.
0 Comments
Leave a Reply. |