VERITAS Storage Foundation 4.1 Intelligent Storage Provisioning Administrator's Guide

Chapter 4, Administering Application Volumes

Removing Logs from a Volume

attribute is ignored. For a DCO volume, ISP may round up the length to make room for the maps

that are required. For a RAID-5 log, a minimum size of three times the full stripe width is imposed,

and the length is rounded up to a integral multiple of the full stripe width.

You can use storage attributes to specify the storage to be used for the logs. For example, the

following command adds a DCO plex to the volume, mirvol1, using disk enc1_7:

# vxvoladm -g mydg -b add log mirvol1 logtype=dco \

use_storage=’"DeviceName"="enc1_7"’

Removing Logs from a Volume

To remove logs from a volume, use the following command:

# vxvoladm [-g diskgroup] [-f] remove log volume [nlogs=number] \

logtype=type [attributes...]

The supported log types are dco and raid5. By default, one RAID-5 log or one plex of a DCO

volume is removed. You can use the nlogs attribute to specify the number of logs or DCO plexes

to remove. You can use storage attributes to specify the storage to be removed. In the following

example, a DCO plex on the disk mydg11 is removed from the volume mirvol1:

# vxvoladm -g mydg remove log mirvol1 logtype=dco\

remove_storage=’"DM"="mydg11"’

To remove all logs of a particular type from a volume, use the following command:

# vxvoladm [-g diskgroup] removeall log volume logtype=type

Note If you use the vxvoladm command to remove logs, you must specify the -f (force) option

to the command if the operation would violate any rules. For example, the rules may imply

that a volume must have minimum number of logs of a particular kind. You must also

specify the -f option when removing a DCO that is in use by DRL configured on a volume.

Data change map (DCM) logs are usually removed automatically as required by VVR

adminstration commands.

Monitoring and Controlling ISP Tasks

ISP performs management of objects (such as subdisks, plexes, and volumes). Once these objects

have been created, VxVM can start performing I/O with them.

The vxvoladmtask command is provided to allow you to manage tasks (ISP tasks) that are

involved in the creation of objects by ISP. The traditional vxtask command allows you to manage

tasks that involve VxVM performing I/O with volumes.