Commands Veritas

8/10/2019 Commands Veritas

http://slidepdf.com/reader/full/commands-veritas 1/93

The vxrecover utility performs plex attach, RAID-5 subdisk recovery, and resynchronize operations for thenamed volumes, or for volumes residin on the specified disks medianame! If no medianame or volume isspecified, the operation applies to all volumes, or to all volumes in the specified disk roup! If -s isspecified, disabled volumes are started! "ith -s and -n, volumes are started, but no other recovery takesplace! Recovery operations are started in an order that prevents t#o concurrent operations on the samedisk! $perations that involve unrelated disks run in parallel!

-b : %erforms recovery operations in the backround! "ith this option, vxrecover runs in the backround toattach stale plexes and subdisks, and to resynchronize mirrored volumes and RAID-5 parity! If this is used#ith -s, volumes are started before recovery beins in the backround!

-c : $perates on cluster-shareable disk roups! This option is used by the cluster reconfiuration utility toeffect recovery on volumes in shared disk roups after the failure of a node in the cluster! Do not use -c asa command-line option! Available only if the &x&' cluster feature is enabled and a license is installed!

-E (tarts disabled volumes or plexes even #hen they are in the )'%T* state! This is useful for startin upvolumes restored by the vxmake utility #hen specified alon #ith the -s option!

-g diskgroup : +imits operation of the command to the iven disk roup, as specified by disk roup ID or disk roup name! If no volume or medianame is specified, all disks in this disk roup are recovered,other#ise, the volume and medianame are evaluated relative to the iven disk roup! "ithout the - option,if no volume and medianame is specified, all volumes in all imported disk roups are recovered other#ise,

the disk roup for each medianame specified is determined based on name uniueness #ithin all diskroups!

-m : Reconizes and enables volumes that #ere moved as a result of a disk roup move, split or .oinoperation!

-n Does not perform any recovery operations! If used #ith -s, volumes are started, but no other actions

are taken! If used #ith -p, vxrecover only prints a list of startable volumes!

-o options : %asses the iven option aruments to the -o options for the vxplex att and vxvol startoperations enerated by vxrecover! *ou can specify an option arument in the form prefix/options to restrictthe set of commands that the -o option is applied to! Defined prefixes are/

• vol applies to all invocations of the vxvol utility 0volume starts, mirror resynchroniza- tions, RAID-5

partity rebuilds, and RAID-5 subdisk recoveries1

• plex, applies to all invocations of the vxplex utility 0used only for attachin plexes1

• attach applies specifically to plex attach operations• start applies specifically to volume start operations

• recover applies to subdisk recoveries

• resync applies to mirror resynchronization and RAID-5 parity recovery!

-p %rints the list of selected volumes that are startable! 2or each startable volume, a line is printedcontainin the volume name, the disk roup ID of the volume, the volume3s usae type, and a list of stateflas pertainin to mirrors of the volume! (tate flas include/

• kdetach indicates that one of the mirrors #as detached by an I4$ failure

• stale means that one of the mirrors needs recovery, but that the recovery is related to an

administrative operation, not an I4$ failure

• stopped prints if neither kdetach nor stale is appropriate for the volume!

-s : (tarts disabled volumes that are selected by the operation! &olumes are started before any other

recovery actions are taken! &olumes are started #ith the -o delayrecover start option! This reuests thatany operations that can be delayed in startin a volume are delayed! That is, only those operationsnecessary to make a volume available for use occur! $ther operations, such as mirror resynchronization,attachin of stale plexes and subdisks, and recovery of stale RAID-5 parity, are typically delayed!

-t tasktag : If any tasks are reistered to track the proress of the operation, marks them #ith the tataskta! This option is also passed to any utilities called to perform recoveries, so all tasks reistered byany utility to perform the recoveries are also taed #ith taskta!

-v : Displays information about each task started by vxrecover! 2or recovery operations 0as opposed tostart operations1, prints a completion status #hen each task completes!

-V : Displays each command executed by vxrecover! The ouput enerated is more verbose than the .obdescriptions printed #ith the -v option!

EXAMPLES : To recover, in the backround, any detached subdisks or plexes that resulted from

replacement of a specified disk, use the command/vxrecover -b medianame

Veritas Commands Page 1 of 93



To monitor the operations, use the command/

vxrecover -v medianame

----------------------------------------------------------------------------------------------------------------------------------------

Vxedit :

-r : to recursively remove a volume and all plex and subdisk records associated #ith it

-f : option is reuired to remove an enabled volume! A volume cannot be removed, even #ith -f, if thecorrespondin volume block or ra# device is open or mounted!

Attribute Values for L!"# ecords

S$nc%ronous : A field that indicates #hether the R+I6 should operate in synchronous or asynchronousmode! In synchronous mode, a #rite reuest to a replicated volume does not complete until the data hasbeen recorded on the (R+ and reached the secondary node! In asynchronous mode, a #rite reuestcompletes as soon as the data is recorded on the (R+! The field may have one of three values/

off mode is asynchronous

override mode is synchronous, but #ill automatically s#itch to asynchronous if the R+I6 becomesinactive due to a disconnection or administrative action

fail mode is synchronous! If synchronous7fail is set and an administrator detaches the %rimary R+I6,

#rites to the R&8 are not failed! 9o#ever, if an R+I6 becomes inactive for any other reason, includin anadministrative detach of the (econdary R+I6, subseuent #rite reuests are failed #ith an )I$ error!

----------------------------------------------------------------------------------------------------------------------------------------

-a : Display all information about each selected record, separated by spaces 0 on the same line 1

-c : Display only &'( and snap ob.ect records!

-d : Display only disk media records!

-f : Display information about each record as one-line output records containin the follo#in fields,

:! Record type, name, ;sae-type, volume association, or plex association 0or - for unassociated plexesand subdisks1

<! )nabled state 0or - for subdisks, disks, or disk roups1, +enth, in units of system sectors

=! %lex association offset 0or - for volumes, plexes, disks, or disk roups1! This field #ill appear as +$8

for lo subdisks!>! ;sae-dependent state 0or - for subdisks1! If an exception condition is reconized 0a plex I4$ failure,

removed or inaccessible disk, or an unrecovered stale data condi- tion1, then that condition is listedinstead of any usae-type-dependent state!

5! The tutil?@ field! This field is set by usae-types as a lockout mechanism!

B! The putil?@ field! This field can be set to prevent associations of plex or subdisk records!

-g diskgroup : Display records from the specified disk roup!

-) : Display only disk roup records!

-% : +ist hierarchies belo# selected records!

-l : Display all information from each selected record!

-n : Display only the names of selected records!

-p : Display only plexes! If a name operand refers to a volume or subdisk, then a dianostic is #ritten to thestandard error!

-r : Display related records of a volume containin subvolumes! 8roupin is done under the hihest levelvolume

-s : Display only subdisks4subvolumes!

-S : Display confiuration summary information! The output consists of a header line follo#ed by a linecontainin the total number of subdisks4subvolumes, plexes, volumes, R&8s, and R+I6s the number of unassociated subdisks4subvolumes and the number of unassociated plexes!

-t : %rint sinle-line output records that depend upon the confiuration record type! 2or disk roups, theoutput consists of the record type 0d1 the disk roup name, and the disk roup ID!

*or subdisks, the output consists of the follo#in fields, from left to riht!

:! Record type 0sd1, name, Associated plex, or dash 0-1 if the subdisk is dissociated

<! ame of the disk media record used by the subdisk, Device offset in sectors




=! (ubdisk lenth in sectors

>! %lex association offset, optionally preceded by subdisk column number for subdisks associ ated tostriped plexes, +$8 for lo subdisks, or the putil?@ field if the subdisk is dissociated! The putil?@ field canbe non-empty to reserve the subdisk3s space for non-volume uses! If the putil?@ field is empty, - isdisplayed for dissociated subdisks!

5! ame of the disk access record used by the subdisk, A strin representin the state of the subdisk/

D)T The subdisk has been detached!

DI( The subdisk is disabled!

d( The subdisk in a RAID-5 plex has failed and the RAID-5 volume is in deraded mode 0d indicates thatthe subdisk is detached, and ( indicates that its contents are stale1!

)A The subdisk is usable!

2AI+ The subdisk has been detached in the kernel due to an error!

D)& The media record on #hich the subdisk is defined has no associated access record!

RC$& The subdisk is part of a RAID-5 plex and has stale content!

R+$C The subdisk has failed and is #aitin to be relocated!

R'$& The media record on #hich the sub disk is defined has been removed from its disk access record

by a utility!*or subvolumes, the output consists of the follo#in fields, from left to riht!

:! Record type 0sv1, Record name Associated plex, or dash 0-1 if the subvolume is dissociated!

<! ame of the underlyin 0layered1 volume record used by the subvolume!

=! umber of layers used in the subvolume, (ubvolume lenth in sectors

>! %lex association offset, optionally preceded by subvolume column number for subvolumes associated tostriped plexes!

5! umber of active plexes, follo#ed by the number of plexes in the underlyin 0layered1 volume!

B! A strin representin the state of the subvolume/ )A if the subvolume is usable DI( if the subvolume isdisabled I$2AI+ if the sub-volume has been detached in the kernel due to an error

*or plexes, the output consists of the follo#in fields, from left to riht/

:! Record type 0pl1, Record name, Associated volume, or - if the plex is dissociated, %lex kernel state

<! %lex utility state! If an exception condition is reconized on the plex 0an I4$ failure, a removed or inaccessible disk, or an unrecovered stale data condition1, then that condition is listed instead of the valueof the plex record3s state field!

=! %lex lenth in sectors, %lex layout type, umber of columns and plex stripe #idth, or - if the plex is notstriped

>! %lex I4$ mode, either R" 0read-#rite1, "$ 0#rite-only1, or R$ 0read-only1

*or volumes, the output consists of the follo#in fields, from left to riht/

:! Record type 0v1, Record name, Replicated volume roup 0R&81, if applicable, &olume kernel state

<! &olume utility state, &olume lenth in sectors, &olume read policy, Referred plex, if used by the read-policy, Associated usae type

*or &'(s, the output consists of the follo#in fields, from left to riht!

:! Record type 0dc1, Record name, Associated volume, or dash 0-1 if the DC$ is dissociated

>! ame of the DC$ volume , or dash 0-1 if no DC$ volume is associated #ith the DC$ ob.ect

*or snap ob+ects, the output consists of the follo#in fields, from left to riht!

:! Record type 0sp1, Record name, ame of the volume #hose snapshot information this snaps recorddescribes, ame of the DC$ #ith #hich this snap record is associated

*or V)s, the output consists of the follo#in fields, in order from left to riht/

:! Record type 0rv1, Record name, Associated R+I6 count, R&8 kernel state 0derived from various flas1

<! R&8 utility state, R&8 primary fla 0primary or secondary1,! Associated data volume count!, The srlvolume!

*or L!"#s, the output consists of the follo#in fields, in order from left to riht/




:! Record type 0rl1, Record name, Associated R&8, or - if the R+I6 is dissociated, R+I6 kernel state0derived from various flas1, R+I6 utility state, The remote host

! The remote disk roup, The remote R+I6

A header line is printed before any record information, for each type of record that could be selected basedon the -&, -%, -v, -p, -s, and -h options! These header lines are follo#ed by a sinle blank line!

-v : Display only volumes! If a name operand refers to a plex or subdisk4subvolume, a dianostic is #rittento the standard error!

-V : Display only R&8s!

To display the names of all unassociated plexes, use the command

vxprint -n -p -e !assoc

To print all subdisks, includin the subdisk name and either the subdisk plex association offset or the putil@field for dissociated subdisks, enter/

vxprint -s -F "%{name:-14} %{pl_offset|putil0}"

The vxprint command can be used to back up ob.ects from one disk roup confiuration #ith the use of thecombined options -mvpsch or -mvpschr! The output should be saved into a file that is maintained outside of the system bein backed up! ;se the follo#in command #ith the saved file to restore the confiuration

----------------------------------------------------------------------------------------------------------------------------------------vxresi,e - chane the lenth of a volume containin a file system

etcvxbinvxresie -bfsx# -F fst$pe# - &is'roup# -t tas'ta# volumene(_lent) me&ianame***#

The vxresize command either ro#s or shrinks both the file system and its underlyin volume to match thespecified ne# volume lenth! The ability to ro# or shrink is file system dependent! (ome file system typesmay reuire that the file system be unmounted for the operation to succeed, as sho#n in the follo#intable/

+xfs ,F

.ounte& F Grow & shrimk Grow only

,nmounte& F Not allowed Grow only

"ote : vxresize #orks #ith &)RITA( 2ile (ystem 0&x2(1 and ;2( file systems only!

In some situations, #hen resizin lare volumes, vxresize may take a lon time to complete! Resizin avolume #ith a usae type other than 2(8) or RAID5 can result in loss of data! ;se the -f option to forceresizin of such a volume!

*ou cannot resize volumes comprised of different layout types! The ne#Elenth operand can bein #ith a F4 - to indicate that the ne# lenth is added to or subtracted from from the current volume lenth!

The medianame operands name disks to use for allocatin ne# space for a volume! These aruments canbe a simple name for a disk media record, or they can be of the form me&ianame/ offset to specify an

offset #ithin the named disk! If an offset is specified, then reions from that offset to the end of the disk areconsidered candidates for allocation!

-o override : Resizes the specified volume and inores any storae-specific uidelines! $verridin theuidelines is not recommended as it can result in incompatible ob.ects, or ob.ects that cannot beadministered by &x&' and any associated soft#are that exploit storae-specific features!

-o verif$ : &erifies that the specified volume can be resized #ithout violatin any storae-specificuidelines, but does not resize the volume! If any uidelines are violated, vxresize exits #ith an error messae!

"ote: These options need a specific license! "ithout the license, vxresize inores the specified option!

(P!("S

-b : %erforms the resize operation in the background ! ;se the vxprint command to determine #hen theoperation completes!

"ote : This option is only honored for ro# operations on non-RAID5 volumes! $ther#ise, it is inored!

-f : 2orces a operation that is usually disallo#ed by vxresize!

-* fst$pe : (upplies the type of the file system to be resized!




-g diskgroup : +imits operation of the command to the iven disk roup!

-s : Reuires that the operation represent a decrease in the volume lenth!

-t tasktag : If any tasks are reistered to track the proress of the operation, mark them #ith the tataskta! The ta specified by taskta is a seuence of up to :B alphanumeric characters!

-x : Reuires that the operation represent an increase in the volume lenth! 2ail the operation other#ise!

----------------------------------------------------------------------------------------------------------------------------------------vxrelocd - monitor &x&' for failure events and relocate failed subdisks

S."(PS!S

4etc4vx4bin4vxrelocd ?-o vxrecoverEarument ?-$ oldEversion ?-s saveEmax ?mailEaddress!!!

&ES'!P!(" : The vxrelocd command monitors &x&' by analyzin the output of the vxnotify command,and #aits for a failure! "hen a failure occurs, vxrelocd sends mail via mailx to root 0by default1 or to other specified users and relocates failed subdisks! After completin the relocation, vxrelocd sends more mailindicatin the status of each subdisk replacement! The vxrecover utility is then run on volumes #ithrelocated subdisks to restore data! 'ail is sent after vxrecover executes!

(P!("S

-o : The -o option and its arument are passed directly to vxrecover if vxrecover is called! This allo#s

specifyin -o slo#?7iodelay to keep vxrecover from overloadin a busy system durin recovery! The defaultvalue for the delay is <5@ milliseconds!

-( Reverts back to an older version! (pecifyin -$ &x&'Eversion directs vxrelocd to use the relocationscheme in that version!

-s Gefore vxrelocd attempts a relocation, a snapshot of the current confiuration is saved in4etc4vx4saveconfi!d! This option specifies the maximum number of confiurations to keep for eachdiskroup! The default is =<!

Mail "otification : Gy default, vxrelocd sends mail to root #ith information about a detected failure and thestatus of any relocation and recovery attempts! To send mail to other users, add the user loin name to thevxrelocd startup line in the startup script 4etc4rc<!d4(@H5vxvm-recover and reboot the system! 2or example,if the line appears as/

nohup vxrelocd root

and you #ant mail also to be sent to user: and user<, chane the line to read/nohup vxrelocd root user: user<

Alternatively, you can kill the vxrelocd process and restart it as vxrelocd root mailEaddress, #heremailEaddress is a user3s loin name! Do not kill the vxrelocd process #hile a relocation attempt is inproress! The mail notification that is sent #hen a failure is detected follo#s this format/

2ailures have been detected by the &)RITA( &olume 'anaer/

failed disks/ medianame failed plexes/ plexname failed lo plexes/ plexname

failin disks/ medianame failed subdisks/ subdiskname

The &olume 'anaer #ill attempt to find spare disks, relocate failed subdisks and then recover the data inthe failed plexes! The medianame list under failed disks specifies disks that appear to have completelyfailed the medianame list under failin disks indicates a partial disk failure or a disk that is in the process of failin! "hen a disk has failed completely, the same medianame list appears under both failed disks andfailin disks! The plexname list under failed plexes sho#s plexes that #ere detached due to I4$ failures thatoccurred #hile attemptin to do I4$ to subdisks they contain! The plexname list under failed lo plexesindicates RAID-5 or DR+ 0dirty reion loin1 lo plexes that have failed! The subdiskname list specifiessubdisks in RAID-5 volumes that #ere detached due to I4$ errors!

Spare Space : A disk can be marked as JJspare!33 This makes the disk available as a site for relocatin

failed subdisks! Disks that are marked as spares are not used for normal allocations unless you explicitlyspecify them! This ensures that there is a pool of spare space available for relocatin failed subdisks andthat this space does not et consumed by normal operations! (pare space is the first space used to




relocate failed subdisks! 9o#ever, if no spare space is available, or the available spare space is notsuitable or sufficient, free space is also used except for those marked #ith the nohotuse fla!

"o%otuse Space : A disk can be marked as JJnohotuse!33 This excludes the disk from bein used byvxrelocd, but it is still available as free space!

eplacement Procedure : After mail is sent, vxrelocd relocates failed subdisks 0those listed in thesubdisks list1! This reuires findin appropriate spare or free space in the same disk roup as the failed

subdisk! A disk is eliible as replacement space if it is a valid &x&' disk 0&' disk1 and contains enouhspace to hold the data contained in the failed subdisk! If no space is available on spare disks, the relocationuses free space that is not marked nohotuse!

To determine #hich of the eliible disks to use, vxrelocd first tries the disk that is closest to the failed disk!The value of JJcloseness33 depends on the controller, taret, and disk number of the failed disk! A disk onthe same controller as the failed disk is closer than a disk on a different controller a disk under the sametaret as the failed disk is closer than one under a different taret!

vxrelocd moves all subdisks from a failin drive to the same destination disk if possible!

If the failin disk is a root disk, vxrelocd #orks only if it can relocate all of the file systems onto the samedisk! If none is found, mail sends the messae/

Rootdisk medianame of disk roup dEname experienced a failure, but there is no suitable disk found torelocate all associated subdisks!

If no spare or free space is found, mail is sent explainin the disposition of volumes that had storae on thefailed disk/

9ot-relocation #as not successful for subdisks on disk dmEname in volume vEname in disk roupdEname! o replacement #as made and the disk is still unusable!

The follo#in volumes have storae on medianame/

volumename

These volumes are still usable, but the redundancy of those volumes is reduced! Any RAID-5 volumes #ithstorae on the failed disk may become unusable in the face of further failures!

If any non-RAID-5 volumes #ere made unusable due to the disk failure, the follo#in messae is included/

The follo#in volumes/

volumename

have data on medianame but have no other usable mirrors on other disks! These volumes are no#unusable and the data on them is unavailable! These volumes must have their data restored!

If any RAID-5 volumes #ere made unavailable due to the disk failure, the follo#in messae is included/

The follo#in RAID-5 volumes/

volumename

had storae on medianame and have experienced other failures! These RAID-5 volumes are no# unusableand data on them is unavailable! These RAID-5 volumes must have their data restored!

If there is spare space available, a snapshot of the current confiuration is saved in4etc4vx4saveconfi!d4dEname!yymmddEhhmmss!mpvsh before attemptin a subdisk relocation! Relocationreuires settin up a subdisk on the spare or free space not marked #ith nohotuse and usin it to replacethe failed subdisk! If this is successful, the vxrecover command runs in the backround to recover the data

in volumes that had storae on the disk!

If the relocation fails, the follo#in messae is sent/

9ot-relocation #as not successful for subdisks on disk dmEname in volume vEname in disk roupdEname! o replacement #as made and the disk is still unusable!If any volumes 0RAID-5 or other#ise1become unusable due to the failure, the follo#in messae is included/

The follo#in volumes/

volumename

have data on dmEname but have no other usable mirrors on other disks! These volumes are no# unusableand the data on them is unavailable! These volumes must have their data restored!

If the relocation procedure #as successful and recovery has beun, the follo#in mail messae is sent/

&olume vEname (ubdisk sdEname relocated to ne#sdEname, but not yet recovered!

After recovery completes, a mail messae is sent relayin the result of the recovery procedure! If therecovery is successful, the follo#in messae is included in the mail/




Recovery complete for volume vEname in disk roup dEname!

If the recovery #as not successful, the follo#in messae is included in the mail/

2ailure recoverin vEname in disk roup dEname!

If the failed disk is a root disk, the follo#in mail messae is sent after attemptin to relocate/

Rootdisk medianame of disk roup dEname experienced a failure, hot-relocation attempted to

move4remirror all the associated subdisks to medianame!(ubdisks from the follo#in volumes ot moved4remirrored/

volumename

If there #ere errors durin root disk relocation, the follo#in messae is added/

)rror/ (ubdisks from the follo#in volumes failed to move4remirror/

volumename

&isabling vxrelocd : If you do not #ant automatic subdisk relocation, you can disable the hot-relocationfeature by killin the relocation daemon, vxrelocd, and preventin it from restartin! 9o#- ever, do not killthe daemon #hile it is doin the relocation! To kill the daemon, run the command/

ps -ef

from the command line and find the t#o entries for vxrelocd! )xecute the command/

kill -H %ID: %ID<

0substitutin %ID: and %ID< #ith the process IDs for the t#o vxrelocd processes1! To prevent vxrelocd frombein started aain, you must comment out the line that starts up vxrelocd in the startup script4etc4rc<!d4(@H5vxvm-recover!

2I+)(

4etc4rc<!d4(@H5vxvm-recover The startup file for vxrelocd!

4etc4vx4saveconfi!d4dEname!yymmddEhhmmss!mpvsh

2ile #here vxrelocd saves a snapshot of the current confiuration before performin a relocation!

---------------------------------------------------------------------------------------------------------------------------------------

vx&mpa&m -f# &isable attribute***#vx&mpa&m enable attribute***#vx&mpa&m et&mpno&e attribute***#vx&mpa&m etsubpat)s attribute***#vx&mpa&m )elp attribute***#vx&mpa&m listctlr attribute***#vx&mpa&m listenclosure attribute***#vx&mpa&m setattr enclosure attribute***#vx&mpa&m start restore attribute***#vx&mpa&m stat error& vx&mpa&m stat restore& vx&mpa&m stop restore

&ES'!P!(" : vxdmpadm lists the paths under a D'% device, ets the D'% device correspondin to apath, lists all the disk controllers on the system, lists all the paths throuh a host disk controller, lists all theD'% nodes throuh a disk array, and enables or disables a host disk controller on the system! vxdmpadm

key#ords select the action to perform, and attributes specify the ob.ects on #hich the action is performed!#E./(&S

disable Disables I4$ to a host disk controller! The command is blocked until all pendin I4$s issuedthrouh the specified disk controller are completed! The disable operation fails if it is issued to a controller connected to the root disk throuh a sinle path! ;se the -f option to force the above operation! disablesupports the attributes ctlr, enclosure, and type!

enable )nables a previously disabled host disk controller to accept I4$s! This operation succeeds only if the controller is accessible to the host and I4$ can be performed on it! "hen connectin Active4%assivedisk arrays in a non-clustered environment, usin enable results in a failback of I4$s to the primary path!enable can be executed to allo# I4$s to the controllers on the system board that #as detached earlier! Attributes that can be specified #ith enable are enclosure, type, and ctlr!

getdmpnode : Displays the D'% device that controls a particular physical path! The physical path is

specified as the nodename attribute! nodename must be a valid path listed in the 4dev4?rdsk directory! ;sethe enclosure attribute #ith etdmpnode to obtain a list of all D'% nodes for the specified enclosure!




getsubpat%s : Displays the paths controlled by the specified D'% node! The dmpnodename specifiedmust be a valid node in the 4dev4vx4?rdmp directory! etsubpaths can also obtain all paths throuh aparticular host disk controller! The attributes supported by etsubpaths are ctlr and &mpno&ename! help

Displays a detailed information about attributes used #ith a particular key#ord!

vx&mpa&m )elp listctlr

listctlr +ists the disk controllers connected to the host! listctlr all lists all controllers on the host!

listenclosure Displays all attributes of the specified enclosure! 2or example/

vx&mpa&m listenclosure 201

displays all attributes associated #ith the disk array )C@:! The attribute all displays the attributesassociated #ith all the enclosures connected to the host!

setattr enclosure : Assins a meaninful name to the specified enclosure! An existin enclosure namemust be specified! vxdmpadm setattr supports the attribute name! 2or example/

vx&mpa&m setattr enclosure 201 name3lab1_enc

The disk array #ill be referred to by this ne# name for all subseuent operations!

start restore (tarts the D'% restore daemon! The restore daemon analyzes the condition of paths everyinterval seconds! The type of analysis depends on the specified policy/

c%eck0all The restore daemon analyzes all paths in the system and revives the paths that are back onlineas #ell as disables the paths that are inaccessible!

c%eck0alternate The restore daemon checks that at least one alternate path is healthy! It enerates anotification on the first occasion that this condition is not met! If there are less than t#o active 0and enabled1paths under a D'% node, vxnotify displays the messae Kdmpnode name has alternate paths!K

"ote : This policy avoids inuiry commands on all healthy paths, and is less costly than checkEall in cases#here a lare number of paths are available! This policy reduces to checkEall if there are only t#o pathsper D'% node!

c%eck0disabled The restore daemon checks the condition of paths that #ere previously disabled due tohard#are failures and revives them if they are back online!

c%eck0periodic The restore daemon performs checkEall once in a iven number of cycles, andcheckEdisabled in the remainder of the cycles!

"ote : This policy may lead to periodic slo#in do#n 0due to checkEall1 if there are lare numbers of pathsavailable!

)e &efault polic$ is c)ec'_&isable&* o c)ane t)e interval or polic$/ $ou must stop t)e restore &aemon an& restart it (it) ne( attributes* o set t)e polic$ to c)ec'_all/ enter:

vx&mpa&m start restore polic$3c)ec'_all

If a controller is disabled usin the follo#in command, the restore daemon does not chane the disabledstate of the path throuh it!

vx&mpa&m &isable ctlr3ctlr

To set the pollin interval to >@@ seconds, enter/

vx&mpa&m start restore interval3400

'aution : The default pollin interval is =@@ seconds! Decreasin this interval can adversely affect systemperformance!

The checkEperiodic policy can be invoked as follo#s/

vx&mpa&m start restore polic$3c)ec'_perio&ic interval3t perio&3n#

"ote: The pollin interval must be specified!

9ere the period n is the number of times that checkEdisabled is invoked before checkEall is invoked! Thisseuence is then repeated! The inteer value n of period can either be specified on the command line, or set as a tunable dmpErestoreEdaemonEcycles in the vx&mp*conf file! 0This reuires a system shutdo#n

and reboot to take effect!1 The value of period specified on the command line takes precedence! If notspecified in either of these #ays, the default period is :@! The checkEalternate policy can be invoked as

follo#s/ vx&mpa&m start restore polic$3c)ec'_alternate interval3tstat errord Displays the number of error daemons runnin!




stat restored Displays the status of the automatic path restoration daemon, the interval of pollin, and thepolicy used to check the condition of paths!

stop restore (tops the &x&' restore daemon! Automatic path failback stops if the restore daemon stops!

A!12ES Attribute values can be specified #ith key#ords in the form attribute7value!

all (pecified #ith the listctlr listenclosure

ctlr (pecifies the host I4$ controller to print information about!dmpnodename (pecifies the D'% metanode name that must be listed in the 4dev4vx4?rdmp directory!

enclosure ;sed #ith the key#ords etsubpaths, etdmpnode, and listctlr!

interval The restore daemon checks the status of disabled paths after every interval seconds!

name "hen used #ith the setattr key#ord, name assins a ne# name to the specified enclosure! The ne#name cannot be more than <5 characters else setattr fails #ith an error messae!

nodename (pecifies the name of a physical path to a disk that must be entered in the 4dev4?rdsk directory!

polic$ &alue can be set to checkEall or checkEdisabled!

t$pe The enclosure type must be one of the enclosure cateories supported by D'%!

EXAMPLES : To list all attributes of all host I4$ controllers on the system, enter/

vx&mpa&m listctlr allTo list all attributes of the disk array enc@, enter/

vx&mpa&m listenclosure enc0

To disable I4$ throuh the host disk controller c<, enter/

vx&mpa&m &isable ctlr3c5

If you then run the listctlr all command, the state of the controller c< is sho#n as disabled! To enable thehost disk controller c<, #hich #as disabled by vxdmpadm disable ctlr7c<, enter/

vx&mpa&m enable ctlr3c5

)xecutin listctlr all after this command sho#s the state of the controller c< as enabled! The follo#inexamples outline the attributes supported by vxdmpadm listctlr!

vx&mpa&m listctlr all

vx&mpa&m listctlr enclosure3enc0 t$pe32

vx&mpa&m listctlr t$pe32

vx&mpa&m listctlr enclosure3enc0

vx&mpa&m listctlr ctlr3c5

The follo#in command lists all paths controlled by the D'% node c<t:d@s<!

vx&mpa&m etsubpat)s &mpno&ename3c5t1&0s5

The follo#in command obtains all paths throuh the host disk controller c<!

vx&mpa&m etsubpat)s ctlr3c5

The follo#in command displays the D'% node that controls the node c=t<d:s<!

vx&mpa&m et&mpno&e no&ename3c6t5&1s5

The follo#in command displays the D'% nodes connected to the enclosure enc@!

vx&mpa&m et&mpno&e enclosure3enc0

The follo#in command assins a ne# name, &'8R%E:, to the enclosure enc@!

vx&mpa&m setattr enclosure enc0 name3+.789_1

To start the restore daemon #ith the default interval 0=@@ seconds1 and default policy 0checkEdisabled1 /

vx&mpa&m start restore

To specify the interval of pollin as >@@ seconds, enter/

vx&mpa&m start restore interval3400

The daemon checks the condition of the paths as specified by the policy attribute! To set the policy ascheckEall, enter/

vx&mpa&m start restore polic$3c)ec'_all




The follo#in command stops the D'% restore daemon the restore daemon is automatically started atsystem startup time #ith default attributes!

vx&mpa&m stop restore

To list the intervals of restore daemons runnin and the number of error daemons, enter /

vx&mpa&m stat restore&

vx&mpa&m stat error& If only a Gase &x&' license is installed, the vxdctl license command displays KD'% 0sinle path enabled1K!If either the 2ull &x&' license or an automatically enerated license 0such as that for the %9$T$ array1is installed, the command displays KD'% 0multipath enabled1K!

----------------------------------------------------------------------------------------------------------------------------------------

vxconfigd - VxVM confiuration daemon

S."(PS!S

vxconfi& -&f'# - &ia_portal# -; in<uir$_portal# -m mo&e# -rreset# -8 re<uest_portal# -x ar#

&ES'!P!(" : The &x&' confiuration daemon, vxconfid, maintains disk confiurations and diskroups in &x&'! vxconfid takes reuests from other utilities for confiuration chanes, and communicates

those chanes to the kernel and modifies confiuration information stored on disk! vxconfid also initializes&x&' #hen the system is booted!

$%TI$(

-d : )uivalent to -m disable, #hich starts vxconfid in disabled mode!

-& diag0portal : (pecifies a rendezvous file path name for dianostic operation connections tovxconfid! 4etc4vx4voldEdia is the default path name! The dianostic portal exists in both the enabled anddisabled operatin modes!

-f : (tarts vxconfid in the foreround! This is often useful #hen debuin vxconfid, or #hen tracinconfiuration chanes! If -f is not specified, vxconfid forks a backround daemon process! The foreroundprocess exits #hen the vxconfid startup processin completes!

-! in3uir$0portal : (pecifies a rendezvous file path name for inuiry operation connections to vxconfid!4etc4vx4voldEinuiry is the default path name! The inuiry portal accepts only opcodes for connection

reuests and uery reuests submitted by vxprint! All other reuests are re.ected! The inuiry portal existsonly #hen vxconfid is operatin in enabled mode!

-k : If a vxconfid process is already runnin, -k kills it before any other startup processin! This is usefulfor recoverin from a hun vxconfid process! 6illin the old vxconfid and startin a ne# one usually doesnot cause problems for volume devices that are bein used by applications, or that contain mounted filesystems!

-m mode (ets the initial operatin mode for vxconfid! %ossible modes are/

boot 9andles boot-time startup of &x&'! This starts the rootd disk roup and any reuired volumes onthe root disk! Goot mode is capable of operatin before the root file system is remounted to read-#rite!vxdctl enable is called later in the boot seuence to trier vxconfid to rebuild the 4dev4vx4dsk and4dev4vx4rdsk directories!

disable (tarts vxconfid in disabled mode! disable creates a rendezvous file for utilities that perform

various dianostic or initialization operations! disable can be used #ith the -r reset option as part of acommand seuence to completely reinitialize &x&' confi! ;se the vx&ctl enable operation to enable

vxconfid!

enable (tarts vxconfid fully enabled 0default1! enable uses the volboot file to bootstrap and load in therootd disk roup! It then scans all kno#n disks for disk roups to import and imports those disk roups!enable also sets up entries in the 4dev4vx4dsk and 4dev4vx4rdsk directories to define all of the accessible&x&' devices! If the volboot file cannot be read, or if the rootd disk roup cannot be imported, vxconfidstarts in disabled mode!

-r reset Resets all &x&' confiuration information stored in the kernel as part of startup processin! Thereset fails if any volume devices are in use! This option is primarily useful for testin or debuin!

- re3uest0portal : (pecifies a rendezvous file path name for reular confiuration and uery reuests!4etc4vx4voldEreuest is the default! The reular reuest portal exists only #hen vxconfid is operatin inenabled mode!




-x arg Turns on various parameters used for debuin or other aspects of vxconfid operation! Thearument, ar, is a decimal number, : throuh H, or a strin! A number value sets the debu informationoutput level and is reuired to obtain any debu messaes!

String arguments include:

boot4volboot0pat% : (pecifies the path name to use for the volboot file! This is primarily useful #ith thestub debu option! The volboot file contains an initial list of disks that are used to locate the root disk roup!

It also contains a host ID that is stored on disks in imported disk roups to define o#nership of disks as asanity check for disks that miht be accessible from more than one host!

'leartempdir : Removes and recreates the 4var4vxvm4tempdb directory! This directory stores confiurationinformation that is cleared after system reboots 0or cleared for specific disk roups on import and deportoperations1! If the contents of this directory are corrupted, due to a disk I4$ failure for example, vxconfid#ill not start up if it is killed and restarted! (uch a situation can be cleared by startin vxconfid #ith -xcleartempdir! This option has no effect if vxconfid is not started in enabled mode!

"ote : It is advisable to kill any runnin operational commands 0vxvol, vxsd, or vxmend1 before usin the -xcleartempdir option! 2ailure to do so may cause these commands to fail, or may cause disastrous butunchecked interactions bet#een those commands and the issuance of ne# commands! It is safe to usethis option #hile runnin the raphical user interface, or #hile &x&' backround daemons are runnin0vxsparecheck, vxnotify, or vxrelocd1!

devprefix4prefixdir : (pecifies a directory path name to prefix for any disk device accessed by vxconfid!2or example, #ith devprefix74tmp, any access to a ra# disk device named c<t:d@s< #ould actually bedirected to the file 4tmp4dev4rdsk4c<t:d@s<! In stubbed mode, vxconfid can operate #ith such files beinreular files! vxconfid only reuires entries in the prefixdir 4dev4rdsk directory in stubbed mode! (ee stubbelo# for more information!

log 5 nolog : +os all vxconfid console output directly to a file! This method of loin is very reliable inthat any messaes output before a system crash are available in the lo file 0if the crash did not corrupt thefile system1! *ou can enable direct vxconfid loin #ith the -x lo arument, and turn it off #ith the -xnolo arument! +oin is disabled by default!

If direct loin is enabled, the default lo file is 4var4vxvm4vxconfid!lo! This option can be used incon.unction #ith syslo L nosyslo! The follo#in command los all debu and error messaes to thespecified lo file/

vxconfid -xH -x lo

logfile4logfilename : (pecifies an alternate vxconfid direct lo file! This option reuires usin the -x loarument!

noautoconfig : vxconfid usually confiures disk devices that can be found by inspectin kernel diskdrivers automatically! These autoEconfiured disk devices are not stored in persistent confiurations, butare reenerated from kernel tables after every reboot! Invokin vxconfid #ith -x noautoconfi prevents theautomatic confiuration of disk devices, forcin &x&' to use only those disk devices confiured explicitlyusin vxdisk define or vxdisk init!

not%reads : Runs vxconfid sinle-threaded!

stub (pecifies not to communicate confiuration chanes to the kernel! stub is typically used as ademonstration mode of operation for vxconfid! In most aspects, a stubbed vxconfid behaves like areular vxconfid, except that disk devices can be reular files and volume nodes are not created! Astubbed vxconfid can run concurrently #ith a reular vxconfid, or concurrently #ith any other stubbed

vxconfid processes, as lon as different rendezvous, volboot, and disk files are used for each concurrentprocess!

$ther &x&' utilities can detect #hen they are connected to a vxconfid that is runnin in stubbed mode!"hen a &' utility detects a stubbed-mode vxconfid, the utility typically stubs out any direct use of volumes or plexes itself! This allo#s utilities to make confiuration chanes in a testin environment thatruns #ithout any communication #ith the kernel or creation of real volumes or plexes!

s$slog 5 nos$slog : vxconfid supports usin the syslo01 library call to lo all of its console messaes0this includes error, #arnin, and notice messaes, but not debu messaes1! *ou can enable syslo01loin usin the -x syslo arument, and turn it off #ith the -x nosyslo arument! *ou can also enablesyslo01 loin at boot-time by editin the &x&' startup scripts!

syslo can be specified alon #ith lo 0described above1 to obtain more reliable loin! 2or example, thefollo#in command los all debu messaes to the specified lo file, and los all error messaes to both

the direct lo file and the syslo!lo file/vxconfid -xH -x lo -x syslo




"ote : syslo01 loin #orks only on systems #here vxconfid is compiled #ith support for the syslo01library calls!

S$nctrace : 2lushes tracefile data to disk, invokin fsync, to ensure that the last entry is included in the fileeven if the system crashes!

timestamp 5 mstimestamp : Attaches a date and time-of-day timestamp to all messaes #ritten byvxconfid to the console! If mstimestamp is used, a millisecond value is also displayed, allo#in detailed

timin of vxconfid3s operation!

tracefile4file : +os all possible tracin information to the specified file!

EX! '(&ES : If errors are encountered, vxconfid #rites dianostic messaes to the standard error output! vxconfid exits if it encounters some serious errors! If an error is encountered #hen importin therootd disk roup durin a normal startup, vxconfid enters disabled mode!

Defined exit codes for vxconfid are/

6 The reuested startup mode completed successfully! This is returned if -f is not used to startup vxconfidas a foreround process! If vxconfid is started as a foreround process, it exits #ith a zero status if vxdctlstop is used to exit vxconfid!

7 The command line usae is incorrect!

8 )nabled-mode operation #as reuested, but an error caused vxconfid to enter disabled mode instead!

This is also returned for boot-mode operation if startup failed! 9o#ever, #ith boot-mode operation, thebackround vxconfid process exits as #ell!

9 The -k option #as specified, but the existin vxconfid could not be killed!

A system error #as encountered that vxconfid cannot recover from! The specific operation that failed isprinted on the standard error output!

; The backround vxconfid process #as killed by a sinal before startup completed! The specific sinal isprinted on the standard error output!

< A serious inconsistency #as found in the kernel, preventin sane operation! This can also happenbecause of version mismatch bet#een the kernel and vxconfid!

= The -r reset option #as specified, but the &x&' kernel cannot be reset! ;sually this means that a volumeis open or mounted!

> An interprocess communications failure 0usually a (TR)A'( failure1! 9as made it impossible for vxconfid to take reuests from other utilities!

? &olumes that must be started early by vxconfid could not be started! The reasons, and possiblerecovery solutions, are printed to the standard error output! The early-started volumes are the root and 4usr file systems, if either or both of those file systems are defined on volumes!

*!LES

4dev4vx4dsk Directory containin block device nodes for volumes!

4dev4vx4rdsk Directory containin ra# device nodes for volumes!

4etc4vx4volboot 2ile containin miscellaneous boot information!

4var4vxvm4tempdb Directory containin miscellaneous temporary files! 2iles in this directory are recreatedafter reboot!

4var4vxvm4vxconfid!lo Default lo file!

----------------------------------------------------------------------------------------------------------------------------------------

vxdg - manae &x&' disk roups

S."(PS!S

vxd ? - diskroup ? -kp ? -o verify L override adddisk ? medianame7accessname!!!

vxd ? -n ne#name ? -h ne#hostid deport diskroup!!!

vxd ? -o verify L override destroy diskroup!!!

vxd flush ?diskroup!!!

vxd ? - diskroup ? -a free ? medianame!!!

vxd ? -Cfst ? -n ne#name import diskroup

vxd ? -T version ? -s ? -o verify L override init roupname ? nconfi7confi-copies ? nlo7lo-copies ? minor7base-minor ? medianame 7 accessname!!!

vxd ? -o override L verify .oin sourced taretd




vxd ? - list ?diskroup!!!

vxd ? -o expand listmove sourced taretd ob.ect!!!

vxd ? -o expand ? -o override L verify move sourced taretd ob.ect!!!

vxd ? - diskroup ? - nohotuse ? medianame!!!

vxd ? -o clean L remove recover diskroup

vxd ? - diskroup ? -f reminor ?diskroup ne#-base-minor

vxd ?- diskroup ?-k repldisk unassoc-medianame7spare-medianame!!!

vxd ? - diskroup ? -k ? -o verify L override rmdisk medianame!!!

vxd - diskroup set attribute7value!!!

vxd ? - diskroup ? - spare ? medianame!!!

vxd ? -Cft ? -o expand ? -o override L verify split sourced taretd ob.ect!!!

vxd ? -T version uprade diskroup

&ES'!P!(" : The vxd utility performs basic administrative operations on disk roups! $perationsinclude the creation of disk roups, the addition of disks to a disk roup, disk roup split4.oin, and diskroup imports and deports!

"ote : A license is necessary to use the Disk 8roup (plit4Moin feature!The behavior of the vxd utility depends upon the key#ord specified as the first operand! A diskrouparument can be either a disk roup name or a disk roup ID! A roupname arument is a disk roupname, not a disk roup ID! An accessname arument refers to a system-dependent disk access name0also referred to as a disk device name1, as stored in the root confiuration by the vxdisk utility! If the slicenumber extension in the disk access record name is not included in the accessname, s< is assumed bydefault! If any other slice is reuired then it should be included in the accessname 0as in c<t:d@s<1! Amedianame arument is an administrative name used to define a disk #ithin a disk roup!

#E./(&S

adddisk Adds the specified disk or disks to a disk roup 0rootd by default1! The disk must not already bepart of a disk roup! The accessname component to a disk specification arument names a disk accessrecord 0essentially a device address specifica- tion1 used to access the disk! If a medianame component isspecified, then it names the disk media record used to define the disk #ithin the disk roup! If no

medianame component is specified, then the disk media record is iven the same name as the diskaccess record!

Addin a disk to a disk roup causes the disk roup3s confiuration to be copied onto the disk 0if the diskhas reions for confiuration copies1! Also, the disk is stamped #ith the system3s host ID, as defined in thevolboot file! If the -k fla is specified, then the disk media name must represent a disk media record that#as previously dissociated from its disk access record #ith -k rmdisk other#ise, a ne# disk media recordis created to represent the disk! "ith the -k option, plexes reuirin recovery are flaed as stale!(pecifyin the -p fla #ith -k packs contiuous subdisks into one subdisk and alins them consecutively ontheir respective disks! ;se the -p option #hen addin a root encapsulated disk or it may not boot correctly!

In a cluster environment, addin a disk to a cluster-shared disk roup fails if the disk is not physicallyaccessible from all .oined nodes in the cluster! If the addition is successful, the disk is stamped #ith thecluster ID and marked #ith the shared fla!

deport Disables access to the specified disk roup! A disk roup cannot be deported if any volumes in thedisk roup are currently open! "hen a disk roup is deported, the host ID stored on all disks in the diskroup are cleared 0unless a ne# host ID is specified #ith -h1, so the disk roup is not reimportedautomatically #hen the system is rebooted!

A disk roup can be renamed on deport by specifyin a ne# disk roup name #ith -n ne#name! A lock canbe assined to an alternate host by specifyin the host ID 0see vxdctl0:'11 of the alternate host! This allo#sthe disk roup to be autoimported #hen the alternate host reboots! 2or example, the -n and -h options canbe combined to export a disk roup to be used as the rootd disk roup for a ne# machine!

In a cluster environment, #hen a cluster-shared disk roup is deported, the cluster ID and shared flastored on all disks in the disk roup are cleared, so the disk roup is not imported automatically #hen thecluster is next started! Tryin to deport a shared disk roup durin a cluster reconfiuration fails!

destro$ Removes a disk roup from the system! ;se this option #hen a disk roup and the information onthe disks is no loner needed! This frees up space for use by other disk roups! A disk roup cannot be

destroyed if any volumes in the disk roup are open 0for example, they are mounted as files systems or inuse by an application such as a database1! vxd destroy can be used only on imported disk roups!




flus% Re#rites all disk on-disk structures manaed by &x&' for the named disk roups! This re#rites alldisk headers, confiuration copies, and kernel lo copies! Also, if any confiuration copies #ere disabled0for example as a result of I4$ failures1, this command re#rites those confiuration copies, and attempts toenable them!

free : +ists free space that can be used for allocatin subdisks! If a disk roup is specified, limit the outputto the indicated disk roup, other#ise list space from all disk roups! If disks are specified, by disk media

name, then restrict the output to the indicated disks! A reion of free space is identified by disk medianame, a physical device ta, an offset relative to the beinnin of the public reion for the media, and alenth!

The physical device ta is a reference that indicates #hich physical device the disk media is defined on! Itappears as a truncated disk access name! If a particular physical device is split into several &x&' diskob.ects, then the device tas for each disk ob.ect are the same! Device tas can be compared to identifyspace that is on the same or on different physical disks! If the - option is specified, then no header isprinted describin output fields! If the -a option is specified, then space on spare disks 0#hich is not reallyallocatable1 is listed in addition to reular free space other#ise, space on spare disks is not listed!

import Imports a disk roup to make the specified disk roup available on the local machine! This makesaccessible any confiuration information stored #ith the disk roup, includin any disk and volumeconfiurations! The disk roup to import is indicated by the diskroup arument, #hich can be either anadministrative disk roup name or a disk roup uniue ID!

Typically, a disk roup is not imported if some disks in the disk roup cannot be found by the local host! The-f option can be used to force an import if, for example, one of the disks is currently unusable or inaccessible!

"ote : Ge careful #hen usin the -f fla because it can import the same disk roup t#ice from dis.ointedsets of disks! This can make the disk roup inconsistent!

"hen a disk roup is imported, all disks in the disk roup are stamped #ith the host3s host ID! Typically, adisk roup cannot be imported if any of its disks are stamped #ith a non-matchin host ID! This provides asanity check in cases #here disks can be accessed from more than one host!

If it is certain that a disk is not in use by another host 0such as because a disk roup #as not cleanlydeported1, then the -C option can be used to clear the existin host ID on all disks in the disk roup as partof the import! A host ID can also be cleared usin vxdisk clearimport! A ne# name can be iven to the diskroup on import usin -n ne#name! If -n is used #ith the -t option, the stored name of the disk roup

remains unchaned, but the importin host kno#s the disk roup under the ne# name other#ise, thename chane is permanent!

Typically, an imported disk roup is reimported automatically #hen the system is rebooted, if at least someof the disks in the disk roup remain accessible and usable! This can be disabled usin the -t option, #hichcauses the import to be persistent only until the system is rebooted!

As an example of the use of -n and -t, a rootd disk roup from one host can be imported on a secondhost, operations 0such as makin repairs to the root volume1 can be performed on the second host and thedisk roup can be iven back to the oriinatin host, #hich can then be rebooted on the repaired diskroup! To do this, identify the disk roup ID for the rootd disk roup #ith

vxdisk -s list, and use that disk roup to import that rootd usin -C to clear import locks, -t for a temporaryname, and -n to specify an alternate name 0to avoid collision #ith the rootd disk roup on the secondhost1! After repair, deport the disk roup usin -h to restore the import lock from the first host! In a cluster environment, use the -s option to import a disk roup as cluster-sharable! This is only valid if the cluster isactive on the host #here the import takes place! )nsure that all the disks in a shared disk roup arephysically accessible by all hosts! A host #hich cannot access all the disks in a shared disk roup cannot .oin the cluster!

The disks in a shared disk roup are stamped #ith the ID of the cluster to #hich the hosts belon and aremarked #ith the shared fla! "hen a host .oins a cluster, it automatically imports disk roups #hose disksare stamped #ith the cluster ID! Tryin to import a shared disk roup durin a cluster reconfiuration fails!

init Defines a ne# disk roup composed of the indicated disks, identified by disk access names! Thisinvolves assinin an internal uniue ID to the roup, storin a pointer to that roup in the rootconfiuration, storin a reference to the roup on all of the named disks that have a disk header, andstorin a disk roup record in the disk roup3s confiuration database! At least one of the disks specifiedmust have space allocated for a confiuration copy!

An existin deported disk roup is destroyed if it has the same name as that specified for the ne# disk

roup! The init cannot complete if a disk is bein used by a disk roup, deported or other#ise! If vxd finds




an unneeded disk roup on the disk, it can be cleaned #ith the vxdisk -f init command! vxd init can thenbe run aain!

If a medianame is specified for use #ith a particular disk, then that medianame names the disk mediarecord used to reference the disk #ithin the disk roup 0for operations such as rmdisk and subdiskcreations1! If no medianame is specified, then the disk media name defaults to accessname! (eevxdisk0:'1 for a discussion of definition and initialization of disk access records!

The init operation can be used to initialize a root disk roup confiuration, #hich is identified by the specialname rootd! If any database locations are listed in the volboot file, then as a special case for initializinrootd, no disk specifications are allo#ed! Disks should be initialized and added to the disk roup as thefirst operations after creatin rootd! (ome or all disks added to the rootd disk roup should also beadded to the volboot bootstrap file! The nconfi and nlo operands can be used to confiure the number of confiuration database copies and kernel lo copies that are maintained for a

disk roup! The confi-copies and lo-copies values are either a decimal number 0includin @ or -:1 or setto all or default! A value of all or -: sinifies that all confiuration or lo copies on all disks in the disk roupare to be maintained! A value of default or @ 0this is also the default value1 sinifies that &x&' is to manaecopies that are distributed in a reasonable pattern throuhout the disks, controllers and enclosures on thesystem! Any other number sinifies that a particular number of copies should be maintained 0or all copies, if that number is larer than the number of available confiuration or lo copies on all disks1!

"hen a specific number 0or default1 is reuested, confiuration copies are distributed across theenclosures on the system! The number of copies in each enclosure is proportional to the number of disks inthat enclosure! "ith the default policy, at least one confiuration and lo copy is maintained for eachenclosure! It is ensured that at least one confiuration and lo copy is maintained for each host controller connected to an enclosure! If this does not result in allocatin at least > copies, then additional copies arespread uniformly across enclosures!

"ote: If a policy other than all is used, then some disks do not have up-to-date, online confiuration and locopies! As a result, it is possible that some number of disk failures can leave a disk roup unusable, even if some disks in the disk roup remain usable! The default policy allocates a sufficient number of copies, in asufficient spread of locations, that such a scenario is very unlikely to occur!

(ince disk roups can be moved bet#een systems, it is desirable that device numbers used for volumes beallocated in separate ranes for each disk roup! That #ay, an administrator can choose ranes such thatall disk roups in a roup of machines can be moved around #ithout causin dev ice number collisions!

Collisions may occur because &x&' stores device numbers in disk roup confiurations, so that the samenumbers can be used after a reboot 0#hich is necessary for use #ith 2(, #hich reuires persistency of device numbers1! If t#o systems use the same device numbers for a set of volumes, and if a disk roupfrom one machine is moved to the other, then &x&' may be forced to temporarily remap some devices!

A base volume device minor number can be set for a disk roup #ith the minor operand! &olume devicenumbers for a disk roup are chosen to have minor numbers startin at this base minor number! 'inor numbers can rane up to :=:@:, so if it is presumed that no more than :@@@ volumes #ould ever becreated in any one disk roup, :=: different ranes of minor numbers are available for different diskroups! A reasonably sized rane should be left at the end for temporary device number remappins 0in theevent that t#o device numbers still conflict1!

If no minor operand is specified on the init command line, then &x&' chooses a random number of at least:@@@ that is a multiple of :@@@, and yields a usable rane of :@@@ device numbers! This default number ischosen such that it does not overlap #ithin a rane of :@@@ of any currently imported disk roups, and does

not overlap any currently allocated volume device numbers!"ote : The default policy is likely to ensure that a small number of disk roups can be mered successfullybet#een a set of machines! 9o#ever, in cases #here disk roups are mered automatically usin fail-over mechanisms, the administrator should select ranes that are kno#n to avoid overlap!

In a cluster environment, the -s option defines a ne# disk roup #hich is cluster-sharable #hile the cluster is active! It is the responsibility of the user to ensure that disks specified as members of a cluster-sharabledisk roup are physically accessible from the hosts that make up the cluster! The disks in a shared diskroup are stamped #ith the ID of the cluster to #hich the hosts belon and are marked #ith the shared fla!"hen a host .oins a cluster, it automatically imports disk roups #hose disks are stamped #ith the cluster ID!

Tryin to create a shared disk roup durin a cluster reconfiuration fails!

"ote : &olumes in shared disk roups must have the same minor number on all nodes in the cluster! If

there is a conflict #hen a node attempts to .oin the cluster, the .oin fails! In that case, the administrator should use the reminor operation on the .oined node0s1 to resolve the conflict! In a cluster #here more thanone node is .oined, the administrator should use a base minor number #hich does not conflict on any node!




If a version is specified #ith the -T option, the disk roup is initialized #ith that disk roup version! Thislimits the operations that can be performed and features that can be used to those supported by thespecified disk roup version! This makes the disk roup compatible #ith releases of &x&' that support thatversion! If no version is specified, the disk roup is initialized #ith the hihest versions supported by therelease of &x&' currently runnin on the system! (ee the vxd uprade operation for more information!

+oin 'oves all ob.ects from the imported source disk roup, sourced, to the imported taret diskroup,

taretd! At the conclusion of the move, sourced is removed!The source disk roup and taret disk roup to be .oined must both be either private or shared! If one diskroup is private and the other is shared, deport and reimport the private disk roup as shared beforeperformin the .oin!

The -o verify and -o override options modify the default behavior of a move, split or .oin operation thatincludes disks from an )'C array! ;sually, if the )'C license is present, the )'C disk compatibility checkis performed for each disk that is involved in a move! If the compatibility check succeeds, the normaloperation takes place! An internal check is made to ensure the confiuration has not chaned since thecompatibility check #as performed! If it #as chaned, the entire process is retried!

If -o verify is specified, the access names of the disks to be moved are returned but the operation does nottake place!

If -o override is specified, the operation is performed #ithout any )'C checkin!

list +ists the contents of disk roups! If no diskroup aruments are specified, then all disk roups are listedin an abbreviated one-line format! If diskroup aruments are specified, then a loner format is used toindicate the status of the disk roup, and of the specified disk roup confiuration!

If the - option is specified, then no header is printed describin output fields! This option has no effect #iththe lon formats enerated #ith diskroup aruments!

In a cluster environment, if the -s option is specified, all cluster-shared disk roups are listed in a one-lineformat! If diskroup aruments are specified, -s has no effect!

listmove Displays a list of all ob.ects, includin all ob.ects in hierarchies, that #ould move from theimported source disk roup, sourced, to the imported taret disk roup, taretd, as implied by thespecified list of ob.ects! The items in the specified ob.ect list must be top-level ob.ects, disk media ob.ectsor disk access ob.ects! This command is used to confirm the validity and ob.ect content of a proposedmove operation #ithout actually movin any ob.ects!

move 'oves the specified ob.ects toether #ith their hierarchies from the imported source disk roup,sourced, to the imported taret disk roup, taretd!

The items in the ob.ect list must be top-level ob.ects, disk media ob.ects or disk access ob.ects! The listmust define a set of self-contained ob.ects, unless the -o expand option is specified! 0(elf-contained meansthat the disks used by the selected ob.ects should not contain any ob.ects that are not selected for themove!1 If the -o expand option is specified, the ob.ect set is expanded to be self-contained!

The source disk roup and taret disk roup must both be either private or shared! If one disk roup isprivate and the other is shared, deport and reimport the private disk roup as shared before performin themove!

(ee vxd .oin for a description of the usae of the -o override and -o verify options!

no%otuse +ists free space that cannot be used by hot-relocation to replace failed subdisks! If a disk- roupis specified, the output is limited to the indicated diskroup, other#ise nohotuse space from all disk roups

is listed! If disks are specified, by disk medianame, then the output is restricted to the indicated disks! Areion of nohotuse space is identified by disk medianame, a physical device ta, an offset relative to thebeinnin of the public reion for the media, and a lenth! The physical device ta is a reference thatindicates #hich physical device the disk media is defined on! It appears as a truncated disk access name! If the - option is specified, then no header is printed describin output fields!

recover Attempts to manually recover an incomplete move, split or .oin operation usin either of the diskroups that #as involved in the operation!

In the event that the recovery cannot complete the operation, the -o clean option clears the '$&) flasfrom the tutil@ fields of the ob.ects in the disk roup!

The -o remove option removes all ob.ects marked #ith the '$&) fla from the disk roup!

reminor Chanes the base minor number for a disk roup, and renumbers all devices in the disk roup to

a rane startin at that number! If the device for a volume is open, then the old device number remains ineffect until the system is rebooted or until the disk roup is deported and re-imported! Also, if you close an






This operation fails if it #ould remove all the disks from the source disk roup, or if an imported disk roupexists #ith the same name as the taret disk roup! An existin deported disk roup is destroyed if it hasthe same name as the taret disk roup 0as is the case for the vxd init command1!

The items in the ob.ect list must be top-level ob.ects, disk media ob.ects or disk access ob.ects! The listmust define a set of selfcontained ob.ects, unless the -o expand option is specified! 0(elf-contained meansthat the disks used by the selected ob.ects should not contain any ob.ects that are not selected for the

move!1 If the -o expand option is specified, the ob.ect set is expanded to be self-contained! The ne#lycreated taret disk roup is imported as shared if the source disk roup is shared other#ise, it is importedas private! The -C, -f, and -t options are import options for the ne# disk roup! (ee the description of vxdimport for details of their use!

(ee vxd .oin for a description of the usae of the -o override and -o verify options!

upgrade ;prades the disk roup to the latest &x&' version! Gy default, the disk roup version is updatedto the runnin version of &x&'! The -T option uprades the disk roup to a specified version! The follo#insection lists each disk roup version, the features it supports, and the &x&' release that introduced it!ote/ (ome &x&' versions are not available on all supported $( platforms!

:@ (upports only the most basic volume manaement features of mirrorin and simple stripin! This format#as introduced in &x&' Release :!<! (tartin #ith &x&' Release =!@, disk roups of version :@ can beimported, but no operations can be performed on the ob.ects it contains 0for example, startin volumes or addin mirrors1! The only operation supported is to uprade the disk roup to a later release!

<@ Introduced support for RAID-5 &olumes, ne# style stripes, recovery checkpointin, disk roupconfiuration4klo copy limitin, and Dirty Reion +oin! This version #as introduced in &x&' Release<!@ and is supported by all subseuent releases of &x&'!

=@ )nabled support for the $racle Resilverin Interface! This version #as introduced in &x&' Release <!<and is supported by all subseuent releases of &x&'!

>@ (upport for 9ot Relocation! Introduced in &x&' Release <!= and is supported by all subseuentreleases of &x&'!

B@ (upport for $nline Relayout, safe RAID-5 subdisk moves, (triped 'irrors, and RAID-5 (napshots!Introduced in Release =!@!

@ on-%ersistent 2astResync, &)RITA( &olume Replicator 0&&R1 enhancements, and ;nrelocate!Introduced in Release =!:!

N@ &)RITA( &olume Replicator 0&&R1 )nhancements! Introduced in Release =!:!:!

H@ Cluster support for $racle Resilverin, disk roup move, split and .oin, Device Discovery +ayer 0DD+1,layered volume support in clusters, ordered allocation, $( independent amin support, and %ersistent2astResync! Introduced in Release =!<! To determine the version of a disk roup, use the vxd listdiskroup command!

ard@are-Specific (ptions (ome environments provide uidelines to optimize &x&'3s interaction #ithintellient storae systems! If these uidelines are present, &x&' follo#s the uidelines #hen creatin diskroups and addin disks to disk roups! Gy default, vxd only allo#s disk roups to contain disks thatconform #ith these uidelines! The follo#in options chane the behavior of vxd/

-o override %erforms the disk roup task and inores any storae-specific uidelines! $verridin theuidelines is not recommended as it can result in incompatible ob.ects, or ob.ects that cannot beadministered by &x&'!

-o verif$ &erifies that the specified disk roup task can be performed #ithout violatin any storae-specificuidelines, but does not perform the task! If any uidelines are violated, vxd exits #ith an error messae!

"ote : These options need a specific license! "ithout the license, vxd inores the specified option!

----------------------------------------------------------------------------------------------------------------------------------------

vxddladm - Device Discovery +ayer subsystem administration

(*$%(I(

etcvxbinvx&&la&m 'e$(or& attribute3value# ***#

vx&&la&m -a | -f | -n# a&&forein {&irname3&irector$ | pat)name3&evice}

vx&&la&m a&&=bo& vi&3ven&or-i& pi&3pro&uct-i&# opco&e3scsi_opco&e#paeco&e3pae_co&e# offset3pae_offset# lent)3sno_lent)#

vx&&la&m exclu&earra$ libname3libname

vx&&la&m exclu&earra$ arra$name3arra$name

vx&&la&m exclu&earra$ vi&3ven&or-i& pi&3pro&uct-i&




vx&&la&m exclu&earra$ vi&3ven&or-i&

vx&&la&m exclu&earra$ pi&3pro&uct-i&

vx&&la&m exclu&earra$ all

vx&&la&m inclu&earra$ libname3libname

vx&&la&m inclu&earra$ arra$name3arra$name

vx&&la&m inclu&earra$ vi&3ven&or-i& pi&3pro&uct-i&

vx&&la&m inclu&earra$ vi&3ven&or-i&

vx&&la&m inclu&earra$ pi&3pro&uct-i&

vx&&la&m inclu&earra$ all

vx&&la&m listexclu&e all#

vx&&la&m listforein

vx&&la&m list=bo& vi&3ven&or-i& pi&3pro&uct-i&##

vx&&la&m listsupport all#

vx&&la&m rmforein {&irname3&irector$ | pat)name3&evice}

vx&&la&m rm=bo& vi&3ven&or-i& pi&3pro&uct-i&#

D)(CRI%TI$ The vxddladm utility is an administrative interface to the dynamic array support facility of the Device Discovery +ayer 0DD+1! This utility lists the types of arrays supported, adds or removes arraysupport from DD+, and allo#s dynamic addition of MG$D support for disks from different vendors! Itadditionally lists supported MG$Ds, and allo#s addition or removal of MG$D support! The vxddladm utility isalso used to customize the set of array libraries that can parti- cipate in device discovery!

#E./(&S

addforeign Adds an entry to the list of forein devices that are not autoconfiurable by &x&'! The dirpathattribute defines a directory that contains device entries that are all to be rearded as forein devices! Thedevicepath attribute defines the absolute path of a sinle forein device! All directory and device entriesmust be specified as absolute pathnames! Device paths may include the O #ildcard! Glock and character devices must be defined separately! $ne of the follo#in options may also be specified to define ho#alternate device entries that are discovered by &x&' are to be treated/

-a : (uppresses any entries for matchin devices in the $(-maintained device tree that are found by the&x&' autodiscovery mechanism! This is the default action if no option is specified to addforein!

-f : Retains any entries for matchin devices found by the &x&' autodiscovery mechanism, andsuppresses any forein device entries that are defined!

-n : Does not suppress any entries! Duplicate entries for forein devices are allo#ed!

add+bod Adds disks havin the specified &ID and %ID in the MG$D cateory 0DI(6(1!

excludearra$ )xcludes the specified array libraries from participatin in device discovery! This does notremove the specified libraries from the system! As a result, vxddladm listsupport displays the correspondindisk arrays!

includearra$ Includes the array libraries previously excluded by excludearray! These can be used for device discovery operations!

listexclude +ists information about the disk array libraries excluded from device discovery functionality!

listforeign +ists information about forein devices that are not autoconfiurable by &x&'!

list+bod +ists information about the types of disks supported in MG$D cateory 0DI(6(1!

listsupport +ists information about supported disk arrays!

rmforein Removes a matchin entry from the list of forein directories and devices!

rm.bod Removes disk #ith the specified &ID and %ID from the MG$D cateory 0DI(6(1! These disks arecateorized as $T9)REDI(6( and are not multipathed!

A!12ES The attribute all selects all ob.ects for an operation! $ther attributes are specified usin theformat attribute7value!

arra$name ame of the array on #hich the operation is performed!

lengt% (ize of the field containin uniue disk serial number!

libname ame of the array library on #hich the operation has to be performed!

offset $ffset on the pae code!




opcode (C(I opcode!

paecode %ae code for (C(I command!

pid %roduct ID of the disk array!

vid &endor ID of the disk array!

"(ES The value for vid and pid should be taken from the output of the vxddladm listsupport command!

These values may be different from the actual vid and pid values of the disks #ithin an array!(ome devices that are controlled by third-party drivers 0for example, )'C %o#er%ath, RA' disks1 may notbe discoverable usin DD+! (uch forein devices can be made available as simple disks to &x&' by usinthe addforein command! D'% is also bypassed for such devices! If a forein device has alias devices inthe $(-maintained device tree, DD+4D'% creates additional disk access records that point to the samephysical device! As such additional records are usually not reuired, creation of these entries can beavoided by specifyin the -a option! After addin or removin forein device entries, use either of thecommands vxdisk scandisks or vxdctl enable to discover the forein devices as simple disks! These disksbehave in the same #ay as autoconfiured disks!

If you specify a vid and pid combination to the excludearray or includearray operations, this excludes or includes all arrays that are supported by the correspondin array library!

----------------------------------------------------------------------------------------------------------------------------------------

vxdiskadm - menu-driven &x&' disk administrator The vxdiskadm script is interactive and prompts you for responses, supplyin defaults #here appropriate!9elp is available at every prompt by enterin a uestion mark 0P1 to display a context-sensitive helpmessae!

To add or encapsulate disks, specify one or more disks #ith a disk-address-pattern-list! The basic formatfor disk addresses is cQtQdQ or enclosure-based names such as enc:E@! *ou can specify .ust the controller and taret to add or encapsulate all the disks at that (C(I address! 2or example, use c<t@ to specify alldisks on controller t#o, taret zero! *ou can specify more than one disk address or address pattern on thecommand line! The #ord all specifies all disks on the system! Disk address names relate directly to devicenode names in the 4dev4dsk and 4dev4rdsk directories!

*ou can use the files 4etc4vx4disks!exclude, 4etc4vx4cntrls!exclude and 4etc4vx4enclr!exclude to exclude disks,controllers and enclosures from use by vxdiskadm! )ach line of disks!exclude specifies a disk to exclude,for example, c@t=d@! )ach line of cntrls!exclude specifies the address of a controller to exclude, for example, c<! )ach line of enclr!exclude specifies an enclosure to be excluded, for example, enc:!

(PEA!("S Add or initialize one or more disks %rompts for one or more disk device addresses! %romptsfor a disk roup 0#hich defaults to rootd1! *ou are also iven the alternative of initializin the disk butleavin it unallocated to a disk roup! If a disk roup is specified, you must name the disk! A default diskname in the form diskQQ is chosen for the root disk roup! If you add a disk to a disk roup other thanrootd, the name is in the form diskroupQQ, such that the names are uniue #ithin all imported diskroups! If a disk roup is specified for the disks, you are prompted to specify #hether to desinate the disksas spares for the disk roup! The disks are then checked to ensure that there is no information already onthem! If there is, you are iven the option of encapsulatin them!

Encapsulate one or more disks %rompts for one or more disk addresses! It then calls vxencap toencapsulate partitions on the named disk!

emove a disk %rompts for a disk, by disk media name! The disk is checked to ensure that no subdisks

reside on the disk! If the disk is in use, the operation fails #ith a recommendation to first move all volumesoff the disk! If this disk is the last disk in a roup, you are also prompted #hether to remove the disk roupfrom the system! The operation then calls vxd rmdisk to remove the disk from its disk roup! If this is thelast disk in its disk roup, vxd deport is used instead!

emove a disk for replacement %rompts for a disk by disk media name! The disk is checked for volumesthat #ould lose all mirrors as a result of the operation! If such volumes exist, those volumes are listed andyou are prompted #hether to continue the operation! The operation calls vxd -k rmdisk to dissociate themedia record from the physical disk! If there are formatted disks available that have disk headers but nodisk roup, you are prompted #hether to use one of these disks as a replacement!

eplace a failed or removed disk %rompts for a disk media name! The named media record must bedissociated from a disk! If the media record is not in the removed state, unused disks are scanned for matchin disk IDs! If a disk #ith a matchin disk ID is found, you are prompted #hether to reattach thatdisk! If a matchin disk is not used, you are prompted for a ne# disk, by device address! If the named

replacement disk has a valid disk header, but is not allocated to a disk roup, you are prompted #hether toreinitialize the disk! If the named replacement disk is listed as allocated to a disk roup or to another host,




you are prompted #hether to continue the operation! If the device is initialized, vxdisksetup is called to setup public and private reions and to create the disk header! 8iven an initialized disk, the operation replacesthe disk in a disk roup #ith vxd -k adddisk!

Mirror volumes on a disk %rompts for a disk, by media name! It then prompts for a destination disk #ithinthe same disk roup, also by media name! (pecifyin no destination disks indicates that any disk can bethe destination! The operation calls vxmirror to mirror the volumes!

Move volumes from a disk %rompts for a disk, by media name! It then prompts for a possible list of destination disks, also by disk media name! (pecifyin no destination disks indicates that any disk issuitable! The operation calls vxevac to move subdisks off the disk!

Enable access to BimportC a disk group %rompts for a disk roup name! The operation calls vxd importto import the disk roup stored on that disk!

emove access to BdeportC a disk group %rompts for a disk roup name! The prompt lists alternate diskroups and the disks 0media name and access name1 that they contain! The operation calls vxd deport!

Enable BonlineC a disk device %rompts for a disk device! The prompt lets you display the disks on thesystem! The operation functions only for disks currently offline! It then makes the disk accessible!

&isable BofflineC a disk device %rompts for a disk device! The prompt lets you display the disks on thesystem! The operation functions only for disks currently online, but not part of any disk roup! It then marksthe disk as offline such that &x&' no loner tries to access the disk!

Mark a disk as a spare for a disk group (ets up a disk as a spare device for its disk roup! A spare diskcan be used to automatically replace a disk that has failed! o space can be used on a disk that is markedas a spare!

urn off t%e spare flag for a disk Removes a disk from the list of spare disks, and returns its space to theeneral pool of available space!

2nrelocate subdisks back to a disk 'oves subdisks #hich #ere hot-relocated follo#in a disk failureback to the oriinal disk, or to a disk #ith a different name, possibly #ith a different offset!

Exclude a disk from %ot-relocation use (ets up a disk to be excluded from use by hot- relocation! Thedisk is marked as nohotuse and it cannot be used by hot-relocation to replace a disk that has failed!9o#ever, it remains available to be used as free space for its disk roup!

'ake a disk available for hot-relocation use Turns off the nohotuse fla on a disk! ;se this option to make adisk available for hot-relocation use! This only applies to disks that #ere previously excluded from hot-relocation use!

%revent multipathin4(uppress devices from &x&'3s vie# )xcludes devices from &x&'3s vie#, or preventsthem from bein multipathed by the dynamic multipathin 0D'%1 driver, vxdmp! There are three #ays of specifyin the devices on #hich these operations are to be performed/

o As a controller for all devices connected throuh the controller!

o As a physical pathname for all devices under that path!

o As a combination of the &endor ID and %roduct ID 0&ID/%ID1 for all devices of that type!

This option also provides a method to define path-roups in case of disks #hich are not multipathed by&x&'! $nly one path from a pathroup #ill be made visible to &x&'! This is useful to avoid duplicateentries for devices that are not multipathed by vxdmp! Allo# multipathin4;nsuppress devices from &x&'3svie# 'akes devices visible to &x&' aain or makes vxdmp multipath these devices aain! This can be

performed only on devices that have already been specified usin the K%revent multipathin4(uppressdevices from &x&'3s vie#K option!

+ist currently suppressed4non-multipathed devices +ists all devices suppressed from &x&'3s vie# and alldevices prevented from bein multipathed by vxdmp!

Chane the disk namin scheme Chanes the disk namin scheme from the cQtQdQ format to enclosure-based! Alternatively, if the existin namin scheme is enclosure-based, it is chaned to cQtQdQ format!

8et the ne#ly connected4zoned disks in &x&' vie# (cans and confiures any ne# disk devices that areattached to the host, disk devices that became online, or fibre channel devices that #ere zoned to host busadapters connected to this host!

+ist disk information Displays a list of disks! *ou can also choose to list detailed information about the diskat a specific disk device address!

9ard#are-(pecific ote (ome environments provide uidelines to optimize &x&'3s interaction #ith

intellient storae systems! If these uidelines are present, &x&' follo#s the uidelines #hen addin disksto disk roups and #hen mirrorin the volumes on a disk! If the operation fails due to these uideline0s1,you are prompted to use the force option! The force option inores any such storae-specific uidelines!




*!LES

4etc4vx4cntrls!exclude (pecifies the address of controllers to exclude from vxdiskadm operations!

4etc4vx4disks!exclude (pecifies the address of disks to exclude from vxdiskadm operations!

4etc4vx4enclr!exclude (pecifies the names of enclosures to exclude from vxdiskadm operations!

----------------------------------------------------------------------------------------------------------------------------------------

vxmake - create &x&' confiuration records

(*$%(I(

vxma'e -p+ # - &is'roup# -o useopt# -, uset$pe# - a|o# -& &escfile#

vxma'e -p+ # - &is'roup# -o useopt# &co name attribute3value***#

vxma'e -p+ # - &is'roup# -o useopt# plex name attribute3value***#

vxma'e -p+ # - &is'roup# rlin' name attribute3value***#

vxma'e -p+ # - &is'roup# rv name attribute3value***#

vxma'e -p+ # - &is'roup# -o useopt# s& name attribute3value***#

vxma'e -p+ # - &is'roup# -o useopt# -, uset$pe# vol name

attribute3value***#&ES'!P!(" The vxmake utility creates subdisk, plex, and volume records for &x&' 0&x&'1! Recordscan be created entirely from parameters specified on the command line, or they can be created usin adescription file!

vxmake can also create a data chane ob.ect 0DC$1 that is used to implement %ersistent 2astResync on avolume! "hen the &)RITA( &olume Replicator 0&&R1 option is available, vxmake can also create R&8and R+I6 records! R&8 and R+I6 records only support en usae!

"ote : The vxprint utility can be used #ith vxmake to perform the functions of a rudimentary confiurationbackup and restore! This should be the primary use of vxmake! ;se of vxmake other than throuh adescription file containin content mostly athered from either the vxprint utility is discouraed in &x&'releases startin #ith =!@! The vxassist utility and the raphical user interface are the recommended meansof creatin ne# or modified volume hierarchies!

If no operands are specified, then a description file is used to specify #hat records to create! Gy default,this description file is read from the standard input! If operands are specified, then the first operand is akey#ord that determines the ob.ect to build, the second operand is the name of the ob.ect to be created,and additional operands specify attributes for the ob.ect to be built! An attribute iven on the command lineis specified in the same manner used #ith the description file 0#ith multiple attributes iven, one attributeper operand1, except that the double-uote convention is not needed! 2or convenience, a special attributeform can be used for subdisks specified directly from the command line! This special attribute form is/

devicepath,offset[,len] or medianame,offset[,len]

The first form specifies a subdisk location by device path, offset #ithin that device, and lenth! The secondform specifies the subdisk location by a disk media record name, offset #ithin the disk3s public reion, andlenth! $ptionally, the lenth can be specified #ith a len7lenth attribute instead! If a device path isspecified, then it must match the device path for the public reion of a kno#n disk in the indicated diskroup! 'ore than one record, includin more than one volume or plex hierarchy, can be specified in a

sinle description file! vxmake attempts to create all records #ithin a sinle transaction, so that either allrecords are created or no records are created! This is the default behavior! The -T option allo#s users toselect transaction control that differs from the default behavior #hen restorin records #ithin a volumehierarchy from a description file! This is particularly helpful #ith layered volume hierarchies that includesubvolumes!

Descriptions of records #ithin a volume hierarchy are filtered throuh a usae-type-specific utility, asappropriate for the usae type, before the records are actually created! (ubdisks and plexes that are notspecified #ithin a volume hierarchy are filtered by the en usae type! The usae- type utilities may chanethe descriptions so that certain fields are inored or set up #ith initial values! %lex or subdisk records to beassociated #ith a volume or plex may also be chaned if the association is indicated in the description,even if the plex or subdisk record is not explicitly specified! A usae type must be specified for everyvolume record, either throuh settin the usetype field in the volume record description, or throuh the -;option to vxmake!

(P!("S




-d descfile (pecify the name of a description file to use for buildin subdisks, plexes, volumes, R&8s andR+I6s! If the descfile option arument is -d, then the description file is read from the standard input! If nooperands are specified, and no descfile is specified, then a description file is read from the standard input!This option is inored for records that are specified directly on the command line!

-g diskgroup (pecify the disk roup for the operation! The disk roup can be specified either by name or by disk roup ID!

-o useopt 8ive usae-type-specific options to the usae type utility!

-p %rint a list of all chanes that #ould be made to the standard output, but do not make those chanes!The output is in the vxmake description file format! All computable and potentially useful attributes areprinted for ne# records! 2or records that #ould be modified, only those attributes that #ould chane areprinted, alon #ith an extra attribute declaration, C9A8)D7yes! In this #ay the -p option performs aprevie# run of the utilities!

This option is intended for use #ith hiher-level tools that previe# record creations, particularly #ith respectto usae-type-dependent attribute modifications!

- This option controls the unit of #ork that vxmake uses to make records #ithin a sinle transaction #henrestorin records from a description file! If the option arument is a or the -T option is absent altoether,then vxmake attempts to create all records #ithin a sinle transaction, so that either all records are createdor no records are created! This behavior is considered the default behavior and it is back#ard- compatible

#ith previous releases of &x&'! If the option arument is o, then one complete top-level ob.ect 0&olumehierarchy, dissociated plex hierarchy, or dissociated subdisk hierarchy1 is created at a time, and if multipletop-level ob.ects are to be created from the same description file, then vxmake attempts to create each onea top-level ob.ect at a time in its o#n transaction! ote that should some ob.ects be creatable and somenot, the confiuration results in those ob.ects that vxmake #as actually able to create! This option can beused for any record hierarchy! Gecause record hierarchies #ith layered volumes may contain manysubordinate records 0such as subvolumes1, the -T o option is particularly useful for safely creatin thesekinds of ob.ects!

-2 uset$pe ;se usetype as the default usae type for volumes! This option has no effect if only subdisksand plexes are created, or if the usae type for a volume is specified directly #ith the description filevariable usetype!

-V Display a list of utilities that #ould be called from vxmake, alon #ith the aruments that #ould bepassed! The -& option performs a previe# run of the utilities the utilities are not actually called, and no

chanes are made to the volume confiuration database!Attribute Specification ules The only attributes that must be specified are the path and len attributes for subdisk records, and a usae type for volume records! In addition, if the layout attribute for a plex record isset to (TRI%), then a positive value must be specified for the st#idth attribute! Also, if no subdisks arespecified for a plex of the (TRI%) layout, the ncolumn attribute must be specified!

Attempts to specify certain attributes are inored by vxmake! (ome attributes are inored by the s#itchout0usae-type independent1 vxmake itself! The usae-type dependent vxmake may cause additionalattributes to be inored!

The sections that follo# provide information on the attributes that can be specified for subdisk, plex, andvolume creation!

Subdisks 2ields that can be specified for subdisks are/ tutil@, tutil:, tutil<, putil@, putil:, putil<, daname,dmname 0or disk1, path, comment, devoffset, dmoffset, len and dmrid! The disk specification for subdisks

uses one of follo#in fields, in order of precedence/ dmrid, dmname, daname, or path! The dmrid field isused, if non-zero! $ne of the other fields is used if defined to a non-empty strin! If the path field is the onlyfield used, it must define the block device path for a partition containin the public reion of a disk in thereuested disk roup!

"ith path, the devoffset field is used as an offset into the partition other#ise dmoffset is used as an offsetinto the private reion! This distinction is important if the public reion does not bein at the beinnin of itspartition! (pecification of a disk in some form 0includin possibly the special forms devicepath,offset,lenthor medianame,offset,lenth1 is reuired! (pecification of the len field is also reuired! All other fields defaultto zero 0for numbers1 or empty strins 0for strins1!

Plexes 2ields that can be specified for plexes are/ tutil@, tutil:, tutil<, putil@, putil:, putil<, comment, layout,ncolumn, st#idth, sd, and losd!

There are no reuired fields for plex records! All fields default to zero 0for numbers1 or empty strins 0for strins1! The layout field defaults to concat!

If the layout field is set to stripe or raid5, then the st#idth attribute must be specified! If the layout field is setto concat, the ncolumn field cannot be specified!




An sd specification names the subdisks to associate #ith the

plex! The specification optionally names the offsets of the

subdisks #ithin the plex! If no offsets are specified, then

the subdisks are directly concatenated in the order indi-

cated! If the sd attribute is specified for a striped plex

and ncolumn is not specified, ncolumn #ill default to the

column of the subdisk #ith the hihest column specification!

As a special case, if ncolumn is not specified and the sd

does not specify columns or offsets for the subdisks, then

each subdisk #ill be placed in its o#n column at an offset

of zero in the order they are specified and the plex3s

ncolumn attribute is set to the number of subdisks speci-

fied!

A losd specification names a subdisk to associate as a spe-

cial lo subdisk for recordin volume activity as part of

the DR+ or DC' loin features!

&x&' =!5 +ast chane/ : $ct <@@< 5

'aintenance Commands vxmake0:'1

&olumes

2ields that can be specified for volumes are/ tutil@,

tutil:, tutil<, putil@, putil:, putil<, comment, usetype,

startopts, readpol, prefname, minor, user, roup, mode, len,

#riteback, #ritecopy, exclusive, primaryEdatavol, lotype,

plex, and dcoEname!

(pecification of a usae type is reuired, either usin the

-; option on the command line, or usin the usetype attri-

bute! (pecification of a usetype attribute overrides a

value specified #ith -;! All other fields have default

values/ readpol defaults to round user and roup both

default to @ 0root1 mode defaults to u7r# 0mode B@@1

#riteback and #ritecopy default to on exclusive defaults to

off len defaults to the lenth of the shortest associated

plex 0or zero, if no plex associations are reuested1 all

other numeric fields default to zero, and all other strin

fields default to empty strins!

A plex specification names the plexes to associate #ith the

volume! The order of plexes in this list is not important!

The value of the prefname field is relevant only if the

readpol attribute is set to prefer!




A dcoEname specification names the data chane ob.ect 0DC$1

to associate #ith the volume!

DC$s

2ields that can be specified for data chane ob.ects 0DC$s1

are/ tutil@, tutil:, tutil<, putil@, putil:, putil<, com-

ment, lo, and dcoEspEnum,

A lo specification defines the volume that is to be associ-

ated as a DC$ volume! A DC$ volume tracks chanes for the

DC$! The follo#in example uses this field to associate

myvolEdcl #ith the DC$ myvolEdcoEob./

vxmake dco myvolEdcoEob. lo7myvolEdcl

dcoEspEnum stores the number of snap records that are asso-

ciated #ith the DC$!

R&8 Records

2ields that can be specified for R&8s are/ tutil@, tutil:,

tutil<, putil@, putil:, putil<, comment, datavol, srl,

rlink, primary, user, roup, mode!

There are no reuired fields for rv records! All fields

default to zero 0for numbers1 or empty strins 0for

strins1! The datavol attribute is a list of the name or

&x&' =!5 +ast chane/ : $ct <@@< B


names 0separated by a comma1 of the data volumes to be asso-

ciated #ith the rv! The srl attribute is the name of the

&)RITA( &olume Replicator lo volume to be associated #ith

the rv! The rlink attribute is a list of name or names

0separated by a comma1 of the R+I6 to be associated #ith

the rv! The order of R+I6s in the list is not important!

(econdary R&8s can have at most one R+I6! The primary

attribute should be set to true for the primary rv and

false for all secondary R&8s!

R+I6 Records

2ields that can be specified for R+I6s are/ tutil@,

tutil:, tutil<, putil@, putil:, putil<, comment, synchro-

nous, localEhost, remoteEhost, remoteEd, remoteErlink,




timeout, packetEsize, protocol, latencyEhihEmark,

latencyElo#Emark, latencyprot, srlprot

There are no reuired fields for R+I6 records! All fields

default to zero 0for numbers1, empty strins 0for strins1,

or off 0for synchronous, latencyprot and srlprot1 #ith the

exception of timeout, packetEsize, latencyEhihEmark, and

latencyElo#Emark, #hich default to some reasonable non-zero

values! The timeout 0milliseconds to #ait for connection

timeouts1 and packetEsize 0bytes per packet1 attributes

should be tailored to the system on #hich &&R is runnin!

The remoteEhost attribute is the name of the remote primary

or secondary node! The remoteEd attribute is the name of

the remote diskroup! The remoteErlink attribute is the name

of the remote R+I6! The protocol arument displays the

transport protocol used by &&R, and is set to the value of

the system tunable parameter volEvvrEtransport 0: for ;D%,

or < for TC%1!

2(8) and 8) ;sae Types

The fsen and en usae-type-specific utilities that support

vxmake are used by the s#itchout vxmake utility as filters

that set defaults for plex and volume states!

(ubdisk fields are set, checked, or modified as follo#s/

len (ubdisk lenths are reuired to be set to a non-

zero value!

tutil@ This field is cleared!

%lex fields are set, checked, or modified as follo#s/


state If the plex is to be associated #ith a volume, the

state field is set to )'%T* other#ise it is

cleared!

&x&' =!5 +ast chane/ : $ct <@@<


&olume fields are set, checked, or modified as follo#s/





state This field is set to )'%T*!

Attempts to associate an existin subdisk or plex #ith a ne#

plex or volume #ill be refused, unless the putil@ field for

the existin record is empty!

The putil@ fields are not set, and their contents are

preserved!

RAID-5 Description

The raid5 usae-type-specific utilities that support vxmake

are used by the s#itchout vxmake utility as filters that set

defaults for plex and volume states!

(ubdisk fields are set, checked or modified as follo#s/

len (ubdisk lenths are reuired to be set to a non-

zero value!


%lex fields are set, checked, or modified as follo#s/


state If the plex is to be associated #ith a volume, the

state field is set to )'%T* other#ise it is

cleared!

&olume fields are set, checked, or modified as follo#s/


state This field is set to )'%T*!

Attempts to associate an existin subdisk or plex #ith a ne#

plex or volume #ill be refused, unless the putil@ field for

the existin record is empty!

The putil@ fields are not set, and their contents are

preserved!

The raid5 specific vxmake utility #ill only allo# one plex

#ith a layout of raid5 to be associated #ith a volume!

%lexes not of the raid5 layout are associated as RAID-5 lo




plexes!

&x&' =!5 +ast chane/ : $ct <@@< N


)A'%+)(

The follo#in is an example of a vxmake description file/

Qrectyp Qname Qoptions

sd disk=-@: disk7disk= offset7@ len7:@@@@

sd disk=-@< disk7disk= offset7<5@@@ len7:@>N@

sd disk>-@: disk7disk> offset7@ len7N@@@

sd disk>-@< disk7disk> offset7:5@@@ len7N@@@

sd disk>-@= disk7disk> offset7=@@@@ len7>>N@

plex db-@: layout7(TRI%) ncolumn7< st#idth7:Bk

sd7disk=-@:/@4@,disk=-@</@4:@@@@,disk>-@:/:4@,disk>-@</:4N@@@,disk>

-@=/:4:B@@@

sd ramd:-@: disk7ramd: len7B>@

comment7K9ot spot for dbvolK

plex db-@< sd7ramd:-@:/>@=<@

vol db usetype7en plex7db-@:,db-@<

readpol7prefer prefname7db-@<

comment7K;ses mem: for hot spot in last 5mK

This description specifies a en type volume that contains

t#o plexes/ a volatile memory disk plex 0db-@<1, #hich is

preferred, and a physical disk plex 0db-@:1! The memory disk

plex is sparse and covers only the last B>@ sectors of the

>@HB@-sector lenth of the volume! The physical disk plex

is striped across t#o <@>N@-sector columns! Column zero con-

tains t#o subdisks and column one contains three subdisks!

The plex offset specified for each subdisk concatenates the

subdisks contiuously in their respective columns!

ote/ 'ore than one attribute may be declared on a sinle

line if separated by one or more tabs or spaces! An attri-

bute and its specified values must be defined on the same

line! Attributes that are specified on lines subseuent to

the first line for an ob.ect definition must be preceded by

one or more tabs or spaces!

2or striped or RAID-5 plex subdisk associations, if one

number is specified for the column and column offset field,

the number is interpreted as a column number and the subdisk




is associated at the end of the column in the order it

appears in the subdisk list! The same subdisk association

list for plex db-@: could be re-#ritten as follo#s/

sd7disk=-@:/@,disk=-@</@,disk>-@:/:,disk>-@</:,disk>-@=/:

The follo#in is an example of a vxmake description file

#hich specifies an R&8 that contains t#o R+I6s, t#o data

volumes and an srl volume/

&x&' =!5 +ast chane/ : $ct <@@< H


Qrectyp Qname Qoptions

rlink rl@: remoteEhost7ebert remoteEd7rootd

remoteErlink7rl@A

rlink rl@< remoteEhost7robert remoteEd7rootd

remoteErlink7rl@G

rv rv@: rlink7rl@:,rl@< primary7true

datavol7vol@<,vol@= srl7srl@:

The follo#in is a simple seuence of commands to create a

hierarchy #ith one subdisk, one plex, and one volume/

vxmake sd disk@-@: disk7disk@ len7:@@@@ S

comment7Kdisk@ subdisk :K

vxmake plex demo-: sd7disk@-@: S

comment7KDemo volume, plex :K

vxmake -; en vol demo plex7demo-: S

comment7KDemo en volumeK

The next example sho#s ho# to use vxmake to create a volume

#ith an associated DC$ ob.ect and DC$ volume/

Q 2irst make the DC$ volume

vxmake sd disk@N-@: disk7disk@N len7<B> S

comment7Kdco vol subdiskK

vxmake plex dcoEplex-: sd7disk@-@: S

comment7Kdco vol plex :K

vxmake -; en vol dcovol plex7dcoEplex-: S

comment7Kdco volK

Q ext make the DC$ itself

vxmake dco DemoEdco lo7dcovol S

comment7Kdco for Demo volK






attribute!!!

vxassist ? options remove volume L mirror L lo U volume

?storae-spec!!! ? attribute!!!

vxassist ? options shrinkby volume lenthchane ? attri-

bute!!!

vxassist ? options shrinkto volume ne#lenth ? attri-

bute!!!

vxassist ? options snapabort volume

vxassist ? options snapback snapvolume

vxassist ? options snapclear volume ?snapEob.ect

vxassist ? options snapprint ?volume

vxassist ? options snapshot volume snapvolume ? attri-

bute!!!

&x&' =!5 +ast chane/ : Mun <@@< :

'aintenance Commands vxassist0:'1

vxassist ? options ? -b snapstart volume ? attribute!!!

vxassist ? options snap#ait volume

D)(CRI%TI$

The vxassist utility is a command-line interface to the &)R-

ITA( &olume 'anaer 0&x&'1 that/

o 2inds space for and creates volumes

o %erforms volume conversion

o Adds mirrors and los to existin volumes

o )xtends and shrinks existin volumes

o 'irates data from a specified set of disks

o %rovides facilities for the online backup of exist-

in volumes




(pecify the appropriate key#ord to vxassist to select an

action to perform!

)ach operation can be applied to only one disk roup at a

time! 2or most key#ords, the volume operand specifies the

volume on #hich to operate! 2or the make operation, attri-

butes that name specific disks can be used to determine a

default disk roup, accordin to the standard disk roup

selection rules described in vxintro0:'1! A specific disk

roup can be specified #ith - diskroup! If no disk attri-

butes are specified, the make operation defaults to usin

the rootd disk roup! *ou can specify an alternate default

disk roup in a defaults file 0usually

4etc4default4vxassist1!

'any vxassist operations can take a set of attributes that

specify such thins as ho# to lay out volumes, or on #hich

sets of disks to build them! There are t#o basic types of

attributes/

o storae specifications

o attribute settins

(torae specification attributes are either simple disk

names 0for example, disk@:1, or roups of disks selected by

controller or taret! 2or example, ctlr/c: specifies all

disks on controller :!

*ou can exclude 0neate1 storae specification by specifyin

the exclamation character 0V1 prefix! 0ote/ *ou may also

&x&' =!5 +ast chane/ : Mun <@@< <


need to escape the V character to prevent it bein inter-

preted by the shell!1 2or example, you can combine the

aruments ctlr/c: and Vtaret/c:t5 to indicate that storae

be allocated from controller :, but not from (C(I taret 5

on that controller!

In (A environments, #here there may be tens of thousands of

disk devices, you can control ho# vxassist should allocate

space by specifyin the reuired set of storae attributes!




(ee the section ;sin (A (torae Attributes #ith vxassist

for details!

$ther attributes are of the form attrname7value these addi-

tional attributes can specify the type of a volume 0mir-

rored, RAID-5, striped, loed1, layout policies 0contiu-

ous, spannin1, mirrorin reuirements 0mirror across con-

trollers1, and constraint parameters 0constrain allocations

to a sinle controller1! (ee the ATTRIG;T)( section belo#

for a complete list of attribute specifications!

If no non-excluded storae specification attributes are

iven, any non-reserved, non-volatile, non-spare, non-

excluded disk can be used to allocate storae! Attributes

may constrain the selection, particularly #ith respect to

the selection of multiple disks! 2or example, the command/

vxassist make mirvol 5@@m layout7mirror,lo mirror7ctlr Vctlr/c<

reuests that vxassist create a ne# mirrored volume on any

disks that are not on controller <! The mirror7ctlr attri-

bute constrains the selection of disks so that the mirrors

are created on different controllers!

6)*"$RD(

addlo Adds a lo or DC$ to a volume!

DC$ is a data chane ob.ect, used for %ersistent

2astResync!

DR+ is a dirty reion lo, used for speedy

recovery of mirrors after a system crash!

(euential DR+ is a form of DR+ that is optimized

for volumes that are #ritten to seuentially, such

as database lo volumes!

DC' is a data chane map, used for fast resyn-

chronization of a secondary R&8 #ith its primary!

'irrored volumes are associated #ith DR+ or

seuential DR+ los!

&x&' =!5 +ast chane/ : Mun <@@< =





RAID-5 volumes are associated #ith RAID-5 los!

Replicated volumes are associated #ith DC' los!

Gy default, #hen addin a lo, vxassist attempts

to determine the correct type of lo to add, even

if no lotype attribute is specified! 2or example,

if the volume is part of an R&8, vxassist attempts

to create a DC' lo!

"hen addin a DR+, RAID-5 or DC' lo to a volume

for the first time, the lolen attribute can be

used to specify the lenth of the lo on addin

additional los, the lolen attribute is inored

and the existin lo lenth is used! If a lolen

#hich is too lare or small to be practical is

specified, vxassist may ad.ust the lenth to a

reasonable size! If no lolen attribute is sup-

plied, vxassist picks an appropriate lo size!

$ther attributes can be specified to indicate

desired properties for the ne# allocations! 'ir-

rorin constraints do not apply to los, thouh

storae constraints can be specified that limit

the los to disk sets already used by the volume!

Addin a DC$ to a volume creates a DC$ ob.ect that

is associated #ith the volume, and a DC$ volume

that is associated #ith the DC$ ob.ect! "hen

created for a non-layered volume #ith at least <

data plexes or for any layered volume, the default

DC$ volume has < DC$ plexes 0mirrors for redun-

dancy1, each of lenth :=< blocks! "hen created

for a non-layered volume #ith a sinle data plex,

the default DC$ volume has a sinle unmirrored DC$

plex of lenth :=< blocks!

ote/ To allo# operation of the dynamic disk roup

split4.oin feature 0see vxd0:'1 for more informa-

tion1, vxassist attempts to place DC$ plexes on

the same disks as the plexes of the correspondin

data volume! This allocation policy may not

succeed if there is insufficient disk space!

vxassist then uses available space in the remain-

in disks of the disk roup! This may prevent cer-

tain disk roup split or move operations if the




DC$ plexes cannot accompany their parent data

volume! To overcome this, you can use storae

specifications to specify explicitly the disks on

#hich the DC$ plexes are to be confiured!

ote/ Addin a DC$ does not enable %ersistent 2as-

tResync on the parent volume unless fastresync7yes

&x&' =!5 +ast chane/ : Mun <@@< >


is also specified!

Addin a DR+ lo to a mirrored volume creates a

sinle lo subdisk and a ne# plex to contain that

subdisk! The ne# plex is then be attached to the

volume! DR+ loin can co-exist #ith DC$!

Addin a RAID-5 lo to a RAID-5 volume involves

creatin a ne# plex that is attached to the volume

as a lo plex!

Addin a DC' lo to a replicated volume adds t#o

los 0by default1, each consistin of a lo plex

and associated subdisk! DC' loin can co-exist

#ith DC$!

convert Converts a volume layout to a mirror-stripe from a

stripe-mirror, or from a mirror-stripe to a

stripe-mirror! Also converts to mirror-concat from

a concat-mirror, or from a mirror-concat to a

concat-mirror!

ro#by L ro#to

Increases the lenth of the named volume to the

lenth specified by ne#lenth 0ro#to1, or by the

lenth specified by lenthchane 0ro#by1!

(pecify the ne# lenth, or chane in lenth, in

&x&' standard lenths 0see

vxintro0:'11! The ro#to operation fails if the

ne# lenth is not reater than the current volume

lenth! The lenth of the volume is increased by

extendin existin subdisks in the volume, or by

addin and associatin ne# subdisks! %lexes that

are not already fully populated 0that is, sparse1




are left unchaned! +o-only plexes are also left

unchaned!

ote/ 2ollo#in a relayout, specify the attribute

layout7nodiskalin to the ro#by and ro#to com-

mands if you #ant the subdisks to be ro#n usin

contiuous disk space!

ote/ "hen you ro# a volume, it is recommended

that you also ro# any file system that is confi-

ured on that volume 0see vxresize0:'11! vxassist

does not resize file systems 0or other uses of the

volume, such as databases1 that reside on the

volume! If necessary, use the appropriate appli-

cation command to ad.ust the layout of data in the

volume after the ro# operation has finished!

"hen a volume is ro#n, the volume may be

&x&' =!5 +ast chane/ : Mun <@@< 5


converted from one layout to another as a side

effect! 2or example, a volume that has the

mirror-stripe layout may be converted to stripe-

mirror #hen it is ro#n! This kind of conversion

is done if vxassist determines that the ne# volume

is too small or lare for the oriinal layout! If

the ne# volume layout is inappropriate, use the

convert operation bet#een layered and non-layered

forms! (ee +ayout (pecifications for a descrip-

tion of the methods used to determine disk lay-

outs!

ote/ *ou cannot resize volumes comprised of dif-

ferent plex layouts! If you try to do so, an

error messae displays statin that the volume

contains differin layouts!

*ou can specify attributes to indicate properties

for the ne# allocations! Any mirrorin con-

straints still apply bet#een all extensions to the

existin mirrors and the other mirrors! 8ro#in

of a volume reuires that the volume be enabled!




"hen the size of a replicated volume chanes, you

can ensure that the size of the DC' is appropriate

by removin all the DC' los and addin them back

#ithout specifyin the lolen attribute!

help Displays information on vxassist usae and &)RITA(

&olume 'anaer attributes! 2or example, to

display information about usin vxassist attri-

butes, enter/

vxassist help attributes

make Creates a volume #ith the specified name and the

specified lenth! The lenth is specified as a

standard &x&' lenth 0see

vxintro0:'11! *ou can specify attributes to indi-

cate various properties and storae locations for

the created volume! (ee +ayout (pecifications for

a description of the methods used to determine

disk layouts!

maxro# Reports the maximum size a volume can ro# iven

its attributes and iven the free storae avail-

able!

maxsize Reports the maximum size a volume could be created

&x&' =!5 +ast chane/ : Mun <@@< B


#ith iven the attributes specified and iven the

free storae available!

mirror Creates a ne# mirror 0or plex1 and attaches it to

the volume! This operation is allo#ed only if the

volume is enabled! Attributes can be specified to

indicate various desired properties and storae

locations for the created volume! Attributes that

constrain mirrorin 0such as reuirin that mir-

rors be on separate roups of disks1 apply bet#een

the existin mirrors of the volume and the ne#

mirror!

Caution/ Do not use vxassist to mirror an encapsu-

lated root disk! Instead use menu item B 0'irror




&olumes on a Disk1 in the vxdiskadm command!

move 'oves subdisks #ithin the named volume off the

excluded storae specified on the command line!

)xcluded storae is specified #ith a prefix of V!

The move operation reuires that at least one

excluded storae specification be iven!

If the volume is enabled, subdisks #ithin detached

or disabled plexes 0or detached lo or RAID-5 sub-

disks1 are moved #ithout recovery of data! If the

volume is not enabled, stale lo or RAID-5 sub-

disks, or subdisks #ithin (TA+) or $22+I) plexes,

are moved #ithout recovery if there are other

subdisks #ithin a non-enabled volume that reuire

movin, the move operation fails!

2or enabled subdisks in enabled plexes #ithin an

enabled volume, the data #ithin subdisks are moved

to the ne# location, #ithout loss of availability

0or redundancy1 of the volume!

relayout Chanes a volume layout or properties! This

operation chanes the number of columns in a

stripe or the stripe #idth of a volume! It also

converts a volume to or from RAID-5,

concatenated-mirror, striped, striped-mirror or

any similar layout!

ote/ The relayout operation internally enerates

uniue data ob.ect names 0for example, v<-Dp@<1

#hen it converts a volume to a specified destina-

tion layout!

ote/ 2ollo#in a relayout, specify the attribute

layout7nodiskalin to the ro#by and ro#to com-

mands if you #ant the subdisks to be ro#n usin

&x&' =!5 +ast chane/ : Mun <@@<


contiuous disk space!

After relayout to a layered form, a volume may be

converted to a non-layered form! 2or example, to




convert from a >-column mirror-stripe to a 5-

column mirror-stripe, first relayout the volume as

a stripe-mirror/

vxassist relayout vol: nstripe75

If you vie# the volume #ith vxprint durin relay-

out, the volume sho#s several subvolumes that are

used durin the chane, and a more complex confi-

uration than usual!

After the ne# column is added, the volume is in

stripe-mirror layout! ;se vxassist convert to con-

vert back to a mirror-stripe layout/

vxassist convert vol: layout7mirror-stripe

ote/ If the system crashes durin relayout or

conversion, the process continues #hen the system

is rebooted! 9o#ever, if the crash occurred dur-

in the first stae of a t#o-stae relayout and

convert operation, only the first stae is subse-

uently completed after rebootin! *ou must run

vxassist convert manually to complete the second

stae!

remove volume L mirror L lo

Deletes the entire volume, one or more mirrors, or

one or more los, accordin to the arument! "hen

deletin a mirror or a lo, specify the storae to

be removed usin the attribute form Vdiskname 0see

(torae (pecifications belo#1! 2or example, to

remove a mirror on disk@:, enter/

vxassist remove mirror vol@: Vdisk@:

(ee vxplex0:'1 for an example of an alternative

method of removin a mirror from a volume!

;se the lotype7 attribute to specify the type of

lo to be removed! 2or example, specify

lotype7drl to remove a DR+ lo!

&x&' =!5 +ast chane/ : Mun <@@< N





ote/ (pecifyin lotype7dco completely removes

the DC$ ob.ect, DC$ volume and any snap ob.ects

that are associated #ith the specified volume, and

also disables 2astResync on the volume!

The alloc7, nmirror7, and nlo7 attributes also

determine the number of mirrors or los remainin

after the remove operation completes! "hen the

number of mirrors drops to :, los are also

removed!

Gy default, vxassist removes : mirror or : lo!

shrinkby L shrinkto

Decreases the lenth of the named volume to the

lenth specified by ne#lenth 0shrinkto1, or by

the lenth specified by lenthchane 0shrinkby1!

(pecify the ne# lenth, or chane in lenth, in

&x&' standard lenths 0see

vxintro0:'11! The shrinkto operation fails if the

ne# lenth is not less than the current volume

lenth!

The lenth of a volume is decreased by removin

and shortenin subdisks to leave each plex #ith

the reuested volume lenth! The freed space can

then be allocated for use by other volumes! +o-

only plexes are left unchaned!

"hen a volume is shrunk, the volume may be con-

verted from one layout to another as a side

effect! 2or example, a volume that has the

mirror-stripe layout may be converted to stripe-

mirror #hen it is shrunk! This kind of conversion

is done if vxassist determines that the ne# volume

is too small or lare for the oriinal layout! If

the ne# volume layout is inappropriate, use the

convert operation bet#een layered and non-layered

forms! (ee +ayout (pecifications for a descrip-

tion of the methods used to determine disk lay-

outs!

ote/ *ou cannot resize volumes comprised of dif-

ferent plex layouts! If you try to do so, an

error messae displays statin that the volume




contains differin layouts!

Caution/ Data can be lost or corrupted if file

systems or other oranized data residin on a

volume are not shrunk before shrinkin the volume!

vxassist does not resize file systems 0or other

uses of the volume, such as databases1 that reside

&x&' =!5 +ast chane/ : Mun <@@< H


on the volume! *ou can use the vxresize command

to shrink file systems on the volume 0see

vxresize0:'11! $ther#ise, use the appropriate

application command to ad.ust the layout of data

in the volume before initiatin the shrink opera-

tion!

snapabort Removes the mirror snapshot #hen a snapstart mir-

ror has been started 0and eventually completed1!

snapback Gy default, finds one plex in the snapshot volume

that has the snapErid field set, and attaches it

to the oriinal volume! If the plex is the last

in a volume, that volume is removed from the disk

roup!

ote/ The snapshot volume and the oriinal volume

must be in the same disk roup!

If the -o allplexes option is specified, all

snapshot plexes in the same disk roup are reat-

tached! Alternatively, if the nmirror7number

attribute is specified, only number plexes are

reattached!

The direction of the resynchronization can be

determined by specifyin either resyncfromoriinal

or resyncfromreplica as the useopt arument to the

-o option! To choose the oriinal volume as the

preferred copy of the data, use -o resyncfromori-

inal! To choose the replica as the preferred

copy of the data, use -o resyncfromreplica!

ote/ *ou must unmount the oriinal volume 0if






in addition to clearin their 2astResync maps!

ote/ )ither of the t#o previous examples stops

%ersistent 2astResync trackin for both the

snapshot volume 0(A%-myvol:1 and the oriinal

volume 0myvol:1 if they are in the same disk

roup!

To support on-%ersistent 2astResync and to be

compatible #ith previous versions of &x&', a sin-

le snapshot volume can be specified as the aru-

ment to snapclear, for example/

vxassist - myoldd snapclear (A%-myoldvol

snapprint Displays the associations bet#een the oriinal

volumes and their respective replicas! If a

volume is specified, output is displayed only for

that volume! An error messae is displayed if

2astResync is not enabled on the volume!

The follo#in information is displayed/

o ame of the oriinal volume!

&x&' =!5 +ast chane/ : Mun <@@< ::


o ames of all snapshot volumes!

o +enth in blocks of the volume, detached plex,

or snapshot plex!

o %ercentae of the snapshot plex or detached

plex that is considered to have been chaned

0dirty1! 2or on-%ersistent 2astResync, #hich

keeps information about chaned reions in a

sinle map for the oriinal volume and its

snapshot volumes, the WDIRT* value is the same

for the oriinal volume as for a snapshot

volume even if #rites are only made to the

snapshot volume! 2or %ersistent 2astResync,

#hich maintains separate trackin maps for the

oriinal volume and each of its snapshot

volumes, the WDIRT* value is based only on #hat




has been #ritten to an individual volume!

In the follo#in example, %ersistent 2astResync is

enabled on volume v:, and on-%ersistent 2as-

tResync on volume v<! & and v indicate the

volume, D% and dp indicate detached plexes, and ((

and ss indicate snapshot plexes!

Q vxassist - myd snapprint v:

& A') ;()T*%) +)8T9

(( (A%$GM A') +)8T9 WDIRT*

D% A') &$+;') +)8T9 WDIRT*

v v: fsen <@>N@

ss (A%-v:Esnp (A%-v: <@>N@ >

dp v:-@: v: <@>N@ @

dp v:-@< v: <@>N@ @

v (A%-v: fsen <@>N@

ss v:Esnp v: <@>N@ @

Q vxassist - myd snapprint v<

& A') ;()T*%) +)8T9

(( (A%$GM A') +)8T9 WDIRT*

D% A') &$+;') +)8T9 WDIRT*

v v< fsen <@>N@

ss -- (A%-v< <@>N@ @

dp v<-@: v< <@>N@ @

v (A%-v< fsen <@>N@

ss -- v< <@>N@ @

&x&' =!5 +ast chane/ : Mun <@@< :<


snapshot Creates a ne# volume by takin one or more

attached temporary mirrors 0#ith state (A%D$)1

to use as its plexes! The nmirror7number attri-

bute can be used to specify the number of mirrors

in a snapshot volume! At least number (A%D$)

plexes must be available in the oriinal volume!

Gy default, one plex is used if nmirrors is not




specified!

The comment attribute may also be used to set the

comment field for the snapshot volume!

The follo#in are examples of the use of the nmir-

ror and comment attributes/

vxassist snapshot nmirror7< S

comment7Kmirrored snapvol for myvolK myvol snapvol

(ome usae types attempt to synchronize any in-

memory data associated #ith the volume 0such as

un#ritten file system modifications1 #hen the

snapshot operation is done! In particular, if the

fsen usae type is used #ith a volume containin

a &)RITA( 2ile (ystem 0&x2(1, then cooperatin

procedures ensure that all file system data is

consistently flushed to the volume! 2or ufs and

s5, the synchronization operation calls sync!

This makes the snapshot a better imae, but it may

leave some inconsistencies bet#een in-memory file

system data and the data residin on the backup

imae!

The snapshot command accepts more than one volume!

All the iven volumes are split atomically 0in a

sinle transaction1! That is, all the iven

volumes are relatively consistent as a result of

takin the snapshot! If you specify the -o allvols

option #ithout ivin any volume names, vxassist

attempts to create a sufficiently lon vxplex com-

mand to take a snapshot of all the volumes in the

disk roup! *ou can use the -o name7pattern option

to specify a name for the ne# volume! $ther#ise,

the default name assined to the ne# volume has

the form (A%Wd-Wv!

snapstart Creates a plex and attaches it to the named volume

as a snapshot mirror! "hen the attach completes,

the plex has state (A%D$) and is a candidate for

selection by the snapshot operation! Attributes

can be specified to indicate the desired proper-

ties of the snapshot mirror!

&x&' =!5 +ast chane/ : Mun <@@< :=





The nmirror7number attribute can be used to

specify the number of snapshot plexes to be

attached to a volume! Gy default, number is :!

ote/ To allo# operation of the dynamic disk roup

split4.oin feature 0see vxd0:'1 for more informa-

tion1, vxassist attempts to avoid placin snapshot

plexes on the same disks as the plexes of the ori-

inal volume or the plexes of its associated DC$

volume! This allocation policy may not succeed if

there is insufficient disk space! vxassist then

uses any other available space in the disk roup!

This may prevent certain disk roup split or move

operations if the snapshot plexes and their asso-

ciated DC$ plexes cannot be physically separated

from the plexes of the oriinal volume or the

plexes of its DC$ volume! To overcome this, you

can use storae specifications to specify expli-

citly the disks on #hich the snapshot plexes are

to be confiured!

snap#ait "aits for an attached mirror to become available

on a volume if a snapstart mirror attach is done

as a backround task 0such as usin the -b

option1! The operation exits #hen the snapshot is

complete! Available snapshot plexes are flaed

#ith state (A%D$)!

$%TI$(

-b %erforms extended operations in the backround!

This option applies to plex consistency recovery

operations for make, ro#to and ro#by, to plex

attach operations started by mirror and snapstart,

to relayout operations started by relayout, and to

the addlo, convert, maxro#, maxsize, move and

remove operations!

-d defaults

(pecifies a file containin defaults for various

attributes related to volume creation and space

allocation! If not specified, this defaults to

4etc4default4vxassist!




-) templateEfile

(pecifies the path name of a template file that

contains (A storae set specifications! (ee the

section ;sin (A (torae Attributes #ith vxassist

for more information!

-f 2orces operations not usually allo#ed by vxassist!

- diskroup

&x&' =!5 +ast chane/ : Mun <@@< :>


(pecifies the disk roup for the operation, either

by disk roup ID or by disk roup name! Gy

default, the disk roup is chosen based on the

medianame operands 0if any1 for the vxassist make

operation, or based on the volume operands for all

other operations!

-n %revents the system defaults file bein read!

-o useopt %asses in options specific to a usae type to the

operation! A certain set of operations are

expected to be implemented by all usae types/

allplexes (pecifies that all available snapshot

plexes in a disk roup are to be reat-

tached to their oriinal volume durin a

snapback operation!

allvols Takes a snapshot of all the volumes in

the disk roup! An error results if one

or more volumes do not have a plex that

is usable for the snapshot!

iosize7size

%erforms copy and recovery operations in

reions #ith the lenth specified by

size, #hich is a standard &)RITA( &olume

'anaer lenth number 0see vxintro0:'11!

(pecifyin a larer number typically

causes the operation to complete sooner,

but #ith reater impact on other

processes usin the volume! The default




I4$ size is typically bet#een > and :<N

kilobytes!

name7pattern

(pecifies the template for namin ne#

snapshot volumes! The pattern consists

of characters and one or more of the

follo#in specifiers/

WW (inle percent character!

Wd ;niue serialization number

expressed as a decimal

inteer!

W Disk roup name!

Wm 'irror3s oriinal name!

Ws (erialization strin expressed

&x&' =!5 +ast chane/ : Mun <@@< :5


as a seuence of one or more

lo#er case letters!

W( (erialization strin expressed

as a seuence of one or more

upper case letters!

Wv &olume name!

Wx ;niue serialization number

expressed as a lo#er-case hex-

adecimal inteer!

W ;niue serialization number

expressed as an upper case

hexadecimal inteer!

The default template name for a ne# snapshot

volume is (A%Wd-Wv!

numchild7number

(pecifies the number of child processes






resyncfromreplica

%erforms a resync usin the data in the

snap plex durin a snapback!

seuential

"hen specified #ith the useopt numchild

for values of number reater than :, the

child processes co-operate in resyn-

chronizin reions of the volume that

are close toether, startin at the

beinnin of the volume and movin to

the end! This creates more overhead for

the resynchronization, but it poten-

tially makes better use of the seuen-

tial read-ahead buffer of the physical

disks!

slo#?7iodelay

Reduces the impact on system performance

of copy operations! Copy and plex con-

sistency recovery operations are usually

a set of short operations on small

reions of the volume 0normally from :B

kilobytes to :<N kilobytes1! This option

inserts a delay bet#een the recovery of

each such reion! A specific delay can

be specified #ith iodelay as a number of

milliseconds, or a default is chosen

0normally <5@ milliseconds1!

-p %rints only the maximum size #ith no text #rappers

0used #ith maxsize and maxro#1!

-r Includes spare disks 0reserved for hot-relocation1

in the calculation!

-t taskta

'arks any tasks that are reistered to track the

proress of an operation #ith the ta taskta!

This option is passed to utilities called by

&x&' =!5 +ast chane/ : Mun <@@< :





vxassist, so any child tasks are also taed #ith

taskta! The ta specified by taskta is a

seuence of up to :B alphanumeric characters!

-; usetype

+imits the operation to volumes that have this

usae type! Any attempt to operate on volumes

that have a different usae type fails!

2or a make operation, this option specifies the

usae type of the volume to be created! $ther#ise,

the default usae type set in the

4etc4default4vxassist file is used, or if such an

entry does not exist, the usae type is set to

fsen!

-v Traces calls to other utilities to determine #hich

&x&' commands vxassist is exe-

cutin!

9ard#are-(pecific $ptions

(ome environments provide uidelines to optimize &x&'3s

interaction #ith intellient storae systems! If these

uidelines are present, &x&' follo#s the uidelines #hen

creatin volumes or allocatin space for volumes! Gy

default, vxassist only creates volumes that conform #ith

these uidelines! The follo#in options chane the behavior

of vxassist operations make, mirror, ro# and shrink /

-o override

%erforms the specified vxassist task for the

specified volume and inores any storae-specific

uidelines! $verridin the uidelines is not

recommended as it can result in incompatible

ob.ects, or ob.ects that cannot be administered by

&x&' and any associated soft#are that exploit

storae-specific features!

-o verify &erifies that the vxassist task for the specified

volume can be performed #ithout violatin any

storae-specific uidelines, but does not commit

or perform any task! If any uidelines are

violated, vxassist exits #ith an error messae!

ote/ These options need a separate license!

"ithout the license, vxassist inores the speci-






combination #ith (A storae set specifications! (ee the

section ;sin (A (torae Attributes #ith vxassist for more

information!

(torae specification attributes have one of the follo#in

forms/

?Vdiskname

(pecifies 0or excludes1 a disk! diskname refers to

a disk media record name in a &)RITA( &olume

'anaer disk roup!

?Vdiskclass/instance

(pecifies 0or excludes1 a set of disks! diskclass

names a particular type of disk roupin 0for

example, ctlr to indicate roups of disks on a

&x&' =!5 +ast chane/ : Mun <@@< :H


sinle controller1, and instance specifies #hich

roupin of that type 0for example c:1! )ach type

of disk class has a particular format for specify-

in instances of the class!

diskclass/same

(pecifies that the allocation must be constrained

to include disks from the same instance of the

iven class! 2or example, a storae specification

of diskparam/same indicates that all disks

selected must have the same basic parameters

0tracksize, cylinder size, size, and revolutions-

per-minute1, but does not specify #hich specific

parameters to use!

The defined disk classes 0and alternate names, or aliases,

for those classes1 are as follo#s/

ctlr 0alias/ c, ctrl, cntrl, controller1

(pecifies disks accessible throuh a controller

roup! All disks accessible throuh the specified

controller name0cQ1 are selected for the opera-

tion!

2or example, consider a confiuration #here t#o




enclosures are connected to a host! The first

throuh controllers c:, c< and the second throuh

controllers c=, c>! The command/

vxassist make vol: :@<> Vctlr/c:

results in disks from the first enclosure bein

excluded from the operation because all disks in

the first enclosure are accessible throuh c:0and

c<1! The command/

vxassist make vol: :@<> Vctlr/c<

has the same effect 0of excludin disks in the

first enclosure1 in the above confiuration! The

command/

vxassist make vol: :@<> layout7mirror nmirror7< mirror7ctl

r

results in the mirrors bein placed across the

controller roups c:, c< and c=, c>!

&x&' =!5 +ast chane/ : Mun <@@< <@


ctype 0alias/ ctlrtype, ctrltype, controllertype1

(pecifies disks from a particular type of con-

troller! The controller type is usually a driver

name! 2or example, on (un machines, the reular

(C(I controller type can be identified as

ctype/esp! As a special case, the (%ARCstorae

Array controller type is specified as ctype/ssa!

da (pecifies a &x&' disk 0&' disk1

by device name 0disk access record name1! 2or

example, c<t:d@s< indicates a &' disk defined on

slice < of disk c<t:d@s<!

device 0alias/ d1

(pecifies all &' disks on a physical disk! The

physical disk is specified in the form cQtQdQ,

#hich indicates the controller, taret ID, and

disk number! Typically, only one &' disk device

is created for each physical disk! 9o#ever, the




vxdisk define operation 0see vxdisk0:'11 can be

used to create additional &' disk devices on

selected partitions!

diskeom 0alias/ eom1

(pecifies disks #ith a particular eometry! The

eometry is specified in the form

cyls!heads!sectors, to indicate the number of

cylinders, heads, and sectors per track, of the

disk! 'any modern drives have variable eometries

0or eometries that do not fit the standard con-

ventions1! 2or such drives, the eometry parame-

ters used are #hatever the drive reports!

diskparam (pecifies disks #ith particular parameters! The

parameters are specified in the form

cyls!heads!sectors!rpm, to indicate cylinders,

heads, sectors per track, and the number of revo-

lutions per minute of the drive! As #ith the disk-

eom parameter, the instances of the diskparam

disk class depend upon the values reported by the

drive, and may not be accurate!

diskrpm 0alias/ rpm1

(pecifies disks #ith a iven rotation speed in

revolutions per minute 0for example, <@@1!

dm 0alias/ disk1

(pecifies a &' disk by disk name 0disk media

record name1 in the disk roup of the volume!

(pecifyin a disk class type of dm or disk is

euivalent to ivin a storae specification #ith

no disk class name!

&x&' =!5 +ast chane/ : Mun <@@< <:


enclr 0alias/ e, enclr, enclosure1

(pecifies disks belonin to a particular enclo-

sure! The enclosure name is obtained usin the

command/

vxdmpadm listenclosure all

2or example, the follo#in command excludes disks




in the enclosure enc: from the operation!

vxassist make vol: :@<> layout7mirror nmirror7< S

Venclr/enc:

taret 0alias/ t1

(pecifies disks #ith the same (C(I taret address

on the same controller! The taret is specified

in the form cQtQ! 2or example, t/c<t> selects

disks on taret > of controller <!

tray (pecifies disks in the same removable tray 0for

(%ARCstorae Array controllers1! Trays in the

(%ARCstorae Array are rouped as t#o (C(I tarets

per tray 0for example, tarets @ and : are in the

same tray1! Trays are specified in the form

cQtrayQ, #here cQ identifies a particular

(%ARCstorae Array controller and trayQ is the

number of a tray 0@ for (C(I tarets @ and :, :

for tarets < and =, or < for tarets > and 51!

2or example, c<tray< selects disks in tray < 0tar-

ets > and 51 of controller <!

The diskeom and diskparam attributes are most often used in

the form diskeom/same and diskparam/same, to indicate that

all disks used for creatin a volume should have similar

characteristics!

$ther Attributes

$ther attributes are of the form attribute7value! The attri-

bute name in an attribute value pair never contains a colon,

so it is possible to specify a disk that has an eual sin

in its name usin the storae specification dm/disk@:7a!

"ithout the dm/ prefix, disk@:7a #ould cause an error indi-

catin an unreconized attribute!

Defined attributes 0and common aliases1 are/

alloc7storae-spec?,storae-spec,!!!

&x&' =!5 +ast chane/ : Mun <@@< <<


(pecifies storae as sinle attributes! This is

useful in a defaults file, so that all attributes




0includin storae specifications1 are in the

attribute7value format! Any number of storae

specifications can be specified, separated by com-

mas! 'ore than one alloc attribute can be speci-

fied, in #hich case they are loically con-

catenated to form one loner list!

ote/ *ou cannot use alloc in combination #ith (A

storae set specifications! (ee the section ;sin

(A (torae Attributes #ith vxassist for more

information!

colEs#itch7size:,size<?,!!!

"hen creatin a volume usin ordered allocation

0-o ordered1, specifies ho# much space to allocate

from each listed disk to a concatenated column

before s#itchin to the next disk! The number of

size aruments 0s#itch points1 determines ho# many

disks are concatenated to form a column! size:

space is allocated from the first disk, size<

space is then allocated from the second disk, and

so on! The s#itch points are applied identically

to all columns in the volume bein created!

2or more information, see the $rdered Allocation

section belo#!

comment7comment

(pecifies a comment to ive to a volume #hen it is

created! This comment can be displayed #ith

vxprint -l, and can be chaned, at a later time,

#ith vxedit set! This attribute can be used #ith

the make and snapshot operations!

dcolen7number 0alias/ dcololen1

(pecifies the lenth of each plex in a DC$ volume!

Gy default, specifyin a lenth on the command

line creates a DC$ volume! The default lenth is

:=< blocks, and any specified value should be an

interal multiple of == blocks bet#een == and <::<

blocks!

diskroup7disk-roup 0alias/ d1

(pecifies the disk roup for an operation! If a

disk roup is specified in a defaults file, then




it .ust specifies the default disk roup to use

for the make operation, if no other means of

determinin the disk roup can be used! If speci-

fied as a command line attribute, it has the same

&x&' =!5 +ast chane/ : Mun <@@< <=


effect as specifyin a disk roup #ith the -

option 0the operation is forced to apply to the

iven disk roup1!

excl7yesLyLonLtrueLnoLnLoffLfalse

(ets or clears the )C+;(I&) fla on the volume!

A volume in exclusive open state can be opened by

only one node in the cluster at a time! 'ultiple

opens of an exclusive volume from the same node

are permitted! on-exclusive volumes can be

simultaneously opened by more than one node!

After a node opens an exclusive volume, every

other node3s open attempt fails until the last

close of the volume by the first opener! (uch an

open failure returns a )G;(* error code!

ote/ $nly available if the &)RITA( &olume 'anaer

cluster feature is enabled!

fastresync7yesLyLonLtrueLnoLnLoffLfalse 0alias/ fmr1

)nables or disables both %ersistent and

onE%ersistent 2astResync! If enabled, 2astResync

is non-persistent if a DC$ ob.ect and a DC$ volume

are not associated #ith a volume, and it is per-

sistent if a DC$ ob.ect and DC$ volume are associ-

ated #ith a volume!

ote/ A license is necessary to use the 2astResync

feature!

fstype7file-system-type

(pecifies the file system type for a ne# volume

0this is used only #ith the make operation1! The

file system type for a volume is usually deter-

mined #hen needed by runnin the fstyp utility

0see fstyp0:'11, but can be specified explicitly!

The file system type parameter is used #ith the




&x&' vxresize utility, as #ell

as #ith volume snapshots, copies, and dissociates

0to select features that are used #ith &)RITA(

2ile (ystem 0&x2(11!

The file system type can be chaned at any later

time #ith the vxedit set operation!

roup7o#nin-roup

(ets the roup ID for a ne# volume! The roup ID

can be specified numerically or #ith a system

roup name! This attribute is used only #ith the

make operation! Gy default, volumes are created

#ith roup @!

&x&' =!5 +ast chane/ : Mun <@@< <>


init7initialization-type

(pecifies ho# to initialize a ne# volume! The

default method 0#hich can be selected explicitly

#ith init7default1 is to call vxvol start to per-

form a default initialization that is specific to

a usae type! A ne# volume can be left uninitial-

ized #ith init7none! The most useful non-default

initialization that can be specified is init7zero,

to clear the volume before enablin it for eneral

use!

layout7layout-spec?,layout-spec,!!!

(pecifies a plex layout type 0RAID-5, mirrored,

unmirrored, striped, cylinder alinment1, and turn

some features on and off 0such as loin1! The

list of layout specifications is iven in the +ay-

out (pecifications section! Gy default, unmir-

rored, non-striped volumes are created #ithout a

lo!

lodisk7disk?,disk,!!!

"hen creatin volumes usin ordered allocation 0-o

ordered1, specifies on #hich disks los should be

created! This attribute must be specified for

RAID-5 volumes unless nolo or noraid5lo is

specified! 2or other types of volume layout, this

attribute is optional, and if not specified any




reuired los are co-located #ith the data!

2or more information, see the $rdered Allocation

section belo#!

lolen7lenth

(pecifies a lo lenth to use for dirty-reion lo

0DR+1 subdisks for mirrored volumes, for RAID-5

lo plexes, or for DC' lo plexes for replicated

volumes! Gy default, specifyin a lo lenth on

the command line creates a lo! Associatin a lo

#ith a mirrored or RAID-5 volume is sufficient to

enable its use!

A DC' lo must be enabled usin the vxrlink com-

mand! This is because it is used for failure

recovery and synchronization of replicated

volumes!

lotype7type

(pecifies the type of lo to use #ith a mirrored

or replicated volume/

dcm (elect DC' 0data chane map1! This is the

default lo type for replicated volumes!

&x&' =!5 +ast chane/ : Mun <@@< <5


dco (elect DC$ 0data chane ob.ect1! 0This is

used to implement %ersistent 2astResync,

#hich is enabled by additionally specifyin

fastresync7on!1 This creates a DC$ ob.ect

and a DC$ volume #ith a plex size specified

by the dcololen attribute, and number of

plexes specified usin the ndcomirror attri-

bute! The default names for the DC$ ob.ect

and DC$ volume are volEdco and volEdcl

respectively for a volume, vol!

If additional loin is reuired, it can be

added to a volume by usin the vxassist add-

lo command! DC$ can co-exist #ith DC' lo-

in for replicated volumes, or #ith DR+ lo-

in for mirrored volumes!




drl (elect DR+ 0dirty reion loin1! This is

the default lo type for mirrored volumes!

drlse

(elect seuential dirty reion loin! This

is identical to drl except that the number of

dirty bits that can be set in the DR+ is lim-

ited to the value of the tunable

voldrlEmaxEseEdirty 0default value is =1!

This is useful on volumes that are usually

#ritten to seuentially, such as database lo

volumes! +imitin the number of dirty reions

allo#s for faster recovery if a crash occurs!

9o#ever, if applied to volumes that are #rit-

ten to randomly, this type of loin can be

a performance bottleneck as it limits the

number of parallel #rites that can be carried

out!

none Do not create a lo!

reion

(elect dirty reion loin identical to

drl!

RAID-5 loin is automatically selected #hen a

lo plex is added to a RAID-5 volume it has no

specific lotype!

If lotype is not specified for a volume, vxassist

attempts to create the optimal type of lo!

maxEnraid5column7number

0alias/ maxraid5columns, maxEnraidcolumn,

maxEnraid5stripe, maxEnraidstripe, maxraidcolumns,

&x&' =!5 +ast chane/ : Mun <@@< <B


maxraid5stripes, maxraidstripes1

(pecifies the default maximum number of stripe

columns for a RAID-5 volume 0default value is N1!

The rules for selectin the default number of




RAID-5 stripe columns are described in the nstripe

attribute!

maxEncolumn7number 0alias/ maxcolumns, maxEnstripe, maxstripes1

(pecifies the default maximum number of stripe

columns, either for a RAID-5 volume 0if

maxEnraid5stripe is not also specified1 or for a

striped plex 0default value is N1! The rules for

selectin the default number of stripe columns is

described in the nstripe attribute!

maxEreionlolen7lenth 0alias/ maxreionlolen1

(pecifies the maximum default dirty reion loin

lo subdisk lenth! If the user does not specify

the dirty reion lo lenth for a volume, #hen

creatin the first lo for a mirrored volume,

vxassist uses a simple formula based on the lo

lenth! The default lenth is not be bounded by

maxEreionlolen 0default value is =<k 0=< kilo-

bytes11!

minEncolumn7number 0alias/ mincolumns, minEnstripe, minstripes1

(pecifies the default minimum number of stripe

columns for either a RAID-5 volume 0if

minEnraid5stripe is not also specified1 or for a

striped plex 0default value is <1! The policy for

selectin a default number of stripe columns is

not allo#ed to select fe#er than this number of

columns!

minEnraid5column7number

0alias/ minraid5columns minEnraidcolumn,

minEnraid5stripe, minEnraidstripe, minraidcolumns,

minraid5stripes, minraidstripes1

(pecifies the default minimum number of stripe

columns for a RAID-5 volume 0default value is =1!

The policy for selectin a default number of

RAID-5 stripe columns is not allo#ed to create a

RAID-5 volume #ith fe#er than minEnraid5stripe

stripe columns!

mirror7?FL-numberLyesLnoLdiskclass?,!!!

(pecifies various mirrorin parameters! 'ultiple

mirrorin parameters can be iven, each separated

by a comma! A decimal number indicates a specific




number of mirrors to create, #hen creatin a

&x&' =!5 +ast chane/ : Mun <@@< <


mirrored volume 0euivalent to nmirror7number1!

yes indicates that volumes should be mirrored by

default 0euivalent to layout7mirror1! no indi-

cates that volumes should be unmirrored by default

0euivalent to layout7nomirror1!

Any other mirrorin parameters specify that

volumes should be mirrored across instances of a

particular disk class 0such as enclr, ctlr or tar-

et1! 2or example, mirror7taret specifies that

volumes should be mirrored bet#een (C(I taret

addresses, and mirror7ctlr specifies that disks in

a mirror should not be on the same controller as

disks in other mirrors #ithin the same volume!

(imilarly, mirror7enclr specifies that disks in a

mirror should not be from the same enclosure as

disks in other mirrors #ithin the same volume!

)ach mirror can contain disks from any number of

instances of the disk class, but different mirrors

cannot use disks from the same instance of the

disk class!

mirrorconfine7diskclass?,diskclass,!!!

(pecifies a reuired list of disk classes for mir-

ror confinement constraints! If this attribute is

specified, a sinle mirror is confined to 0that

is, allocated from1 a roup of disks belonin to

a specific disk class! 'ultiple mirrors can be

allocated from a sinle disk class! 'ultiple disk

classes cannot be used to allocate a mirror! The

follo#in example specifies that each mirror is

allocated from devices belonin to a sinle (C(I

taret and multiple mirrors can be allocated from

devices belonin to a sinle (C(I taret/

mirrorconfine7scsiEtaret

mode7permissions

(pecifies the permissions for the block and char-




acter device nodes created for a ne# volume! The

mode can be specified either as an octal number or

symbolically! A symbolic mode is specified usin

the syntax iven in chmod0:1! This attribute is

used only #ith the make operation! The default

mode for a volume ives read and #rite access only

to the o#ner!

ndcmlo7number 0alias/ ndcmlos, ndcms, ndcm1

(pecifies the number of DC' lo plexes to create!

The default number is < #hich creates a mirrored

&x&' =!5 +ast chane/ : Mun <@@< <N


DC' lo!

ndcomirrors1

ndcomirror7number 0alias/ ndco, ndcos, ndcolo, ndcolos,

(pecifies the number of DC$ plexes to create for a

DC$ volume! A value for number of < or reater

creates a mirrored DC$ volume! 2or non-layered

volumes, the default number is set to the lesser

of the number of data plexes in the parent volume

or <! 2or layered volumes, the default number is

set to <!

nlo7?FL-number, 0alias/ nlos, los1

(pecifies the number of los to create, by

default, for a RAID-5, mirrored, or replicated

volume 0assumin that los are to be created1! The

number of los to create can be specified indepen-

dently for RAID-5 or mirrored volumes usin the

nraid5lo and nreionlo attributes! 2or a relay-

out, this value can be preceded by a F or a - to

add or subtract los!

nmirror7?FL-number, 0alias/ nmirrors, mirrors1

(pecifies the number of mirrors to create #hen

mirrorin a volume 0default value is <1!

2or a relayout, this value can be preceded by a F

or a - to add or subtract mirrors! The value can

also be specified as srcEnmirror to preserve the

number of mirrors!




This attribute is also used to specify the number

of snapshot plexes to be attached to a volume by a

snapstart operation, and the number of plexes in a

snapshot volume for snapshot and snapback opera-

tions! 2or a snapshot, there must be number (A%-

D$) plexes available in the oriinal volume! 2or

a snapback, there must be number snapshot plexes

available in the snapshot volume 0#hich must also

be in the same disk roup as the oriinal volume1!

nraid5lo7number

0alias/ nraid5los, raid5los, nraidlo, nraid-

los, raidlos1

(pecifies the number of lo plexes to create for a

ne# RAID-5 volume 0default value is :1! This

attribute is used only #ith the make operation!

nraid5stripe7?FL-number

0alias/ raid5stripes, nraid5column, nraidstripe,

raidstripes, raidcolumns, nraidcolumn,

&x&' =!5 +ast chane/ : Mun <@@< <H


raid5columns1

(pecifies the number of stripe columns to use #hen

creatin a ne# RAID-5 volume 0the default is to

ad.ust the number to available disks1! This attri-

bute is used only #ith make and relayout opera-

tions! 2or the relayout operation, the default is

the same number of stripe columns the volume has!

2or a relayout, this value can be preceded by a F

or a - to add or subtract columns!

nreionlo7number 0alias/ nreionlos, reionlos, ndrl1

(pecifies the number of lo subdisks to create for

a ne# mirrored volume 0default value :1! This

attribute is used only #ith the make operation,

and only if loin is reuested for the volume!

nstripe7?FL-number

0alias/ stripes, ncolumn, ncolumns, ncol, ncols,




columns, cols1

(pecifies the number of stripe columns to use #hen

creatin a ne# RAID-5 volume 0#ith the make opera-

tion1 or #hen creatin a striped plex 0#ith the

make, relayout, mirror, and snapstart operations1!

The default is to ad.ust to the number of avail-

able disks! 2or the relayout operation, the

default is the same number of stripe columns the

volume has! 2or a relayout, this value can be pre-

ceded by a F or a - to add or subtract columns!

probeEranularity7size

(pecifies the ranularity for the maxsize reuest!

The default size value is :m 0: meabyte1!

raid5Estripeunit7#idth

0alias/ raid5Est#id, raid5EstE#idth,

raid5Est#idth, raidEstE#idth, raidEstripeunitsize,

raid5Estripeunitsize, raid5Estripeunit#idth,

raidEst#id, raidEst#idth, raidEstripeunit,

raidEstripeunit#idth1

(pecifies the stripe unit size to use #hen creat-

in a ne# RAID-5 volume 0default value is :Bk 0:B

kilobytes11! This attribute is used only #ith the

make operation!

raid5lolen7lenth 0alias/ raidlolen1

(pecifies the lo lenth to use #hen addin the

first lo to a RAID-5 volume! The default is four

times the full stripe #idth 0the stripe unit size

times the number of stripe columns1!

&x&' =!5 +ast chane/ : Mun <@@< =@


reionlolen7lenth 0alias/ drllolen, drllen1

(pecifies the lo subdisk lenth to use #hen

addin the first lo subdisk to a mirrored volume!

The default is chosen based on a formula involvin

the volume lenth!

salcontact7no

If (A Access +ayer 0(A+1 is installed and runnin




on a host, by default vxassist contacts the (A+

daemon 0sald1 to obtain storae roup specific

information! To prevent vxassist contactin sald,

set the salcontact attribute to no!

salEusername7username

(A+ authentication reuires a user name and pass-

#ord to be passed to sald 0see the vxspcsho#0:'1

manual pae for details of ho# to add details of a

(A+ user to &x&'1! The salEusername attribute is

used to define the user name 0for example,

salEusername7admin1 that is to be authenticated by

(A+! If no user name is specified to vxassist,

the user name 0such as root1 under #hich vxassist

is runnin is used!

spare7noLonlyLyes

Controls the use of spare disks #hen hot-

relocation is performed!

If set to yes, spare disks are used! If necessary,

free space is also used on disks that have been

marked nohotuse7off! This is the default

behavior!

If set to only, relocation storae is allocated

usin only spare disks!

If set to no, spare disks are not used! Alterna-

tively, do not mark any of your disks as spares

and do not mark them as available for use by hot

relocation!

stripe7diskclass?,!!!

(pecifies that volumes should be striped across

instances of a particular disk class! 2or example,

stripe7taret specifies that volumes should be

striped bet#een (C(I taret addresses! )ach column

can contain disks from any number of instances of

the disk class, but different columns cannot use

disks from the same instance of the disk class!

stripe-mirror-col-trier-pt7size

(pecifies a size that triers the creation of a

&x&' =!5 +ast chane/ : Mun <@@< =:






user7o#nin-user

(pecifies the user ID for a ne# volume 0default

value is root1! The user ID can be specified

numerically or it can be a system loin name!

This attribute is used only #ith the make opera-

tion!

usetype7volume-usae-type

&x&' =!5 +ast chane/ : Mun <@@< =<


(pecifies the usae type to use #hen creatin a

ne# volume 0default value is raid5 for RAID-5

volumes other#ise fsens the default1! This

attribute is only used #ith the make operation!

The usae type can also be specified usin the -;

option!

#antalloc7storae-spec?,storae-spec,!!!

(pecifies a set of desired storae specifications!

This is useful in a defaults file to indicate

desired storae specifications that should be dis-

carded if they fail to yield a reasonable set of

allocations! The format is the same as for the

alloc attribute 0a comma-separated list of storae

specifications1!

2or example, a defaults file can name a specific

controller type to use for allocations, if possi-

ble! "hen all disks on that type of controller are

full, other controllers are used!

ote/ *ou cannot use #antalloc in combination #ith

(A storae set specifications! (ee the section

;sin (A (torae Attributes #ith vxassist for

more information!

#antmirror7diskclass?,diskclass,!!!

(pecifies a desired list of disk class mirrorin

specifications! This is useful in a defaults file

to indicate a set of desired mirrorin constraints

that can be dropped if they fail to yield a rea-

sonable set of allocations!




2or example, a defaults file can specify that

volumes should be mirrored bet#een disks on dif-

ferent controllers in the system! The constraint

is dropped if the set of volumes builds up in such

a #ay that a ne# volume cannot be mirrored across

controllers!

#antmirrorconfine7diskclass?,diskclass,!!!

(pecifies a list of disk classes for mirror con-

finement constraints! A sinle mirror is confined

to 0that is, allocated entirely from1 a roup of

disks belonin to a sinle disk class!

This is useful in a defaults file to indicate a

set of mirror confinement constraints that can be

dropped if they fail to yield a reasonable set of

allocations! 2or example, a defaults file can

specify that a sinle mirror be confined to disks

of the same vendor/

&x&' =!5 +ast chane/ : Mun <@@< ==


#antmirrorconfine7vendor

If vxassist cannot allocate a mirror from disk

devices of one vendor, this constraint is dropped

and the mirror is allocated from disk devices of

other vendors!

#antstripe7diskclass?,diskclass,!!!

(pecifies a desired list of disk class strippin

specifications! This is useful in a defaults file

to indicate a set of desired strippin constraints

that can be dropped if they fail to yield a rea-

sonable set of allocations!

2or example, a defaults file can specify that

volumes should be striped bet#een disks on dif-

ferent controllers in the system! The constraint

is dropped if the set of volumes builds up in such

a #ay that a ne# volume cannot be striped across

controllers!




+ayout (pecifications

The layout attribute specifies a comma-separated list of

simple parameters 0#ith no aruments1 that apply to vxassist

operations!

T#o ne# layouts #ere added in the =!@ release of &x&'/

stripe-mirror and concat-mirror! In previous releases,

#henever mirrorin #as used, the mirrorin had to happen

above stripin or concatenation! o# there can be mirrorin

both above and belo# stripin and concatenation!

%uttin mirrorin belo# stripin mirrors each column of the

stripe! If the stripe is lare enouh to have multiple sub-

disks per column, each subdisk can be individually mirrored!

A similar concatenated volume #ould also mirror each subdisk

individually! These ne# layouts enhance redundancy and

reduce recovery time in case of an error! In a mirror-

stripe layout, if a disk fails, the entire plex is detached,

thereby losin redundancy on the entire volume! "hen the

disk is replaced, the entire plex must be brouht up to

date! Recoverin the entire plex can take a substantial

amount of time! If a disk fails in a stripe-mirror layout,

only the failin subdisk must be detached, and only that

portion of the volume loses redundancy! "hen the disk is

replaced, only a portion of the volume needs to be

recovered!

The ne# volume layouts are more complex than the older

volume layouts! Gecause the advantaes of recovery time and

improved redundancy are more important for larer volumes,

&x&' =!5 +ast chane/ : Mun <@@< =>


it is best to continue usin mirror-stripe and mirror-concat

for most volumes and only use stripe-mirror and concat-

mirror for very lare volumes!

*ou can specify layout7mirror-stripe or layout7stripe-mirror

to implement the desired layout! If you specify

layout7stripe,mirror or layout7mirror,stripe, vxassist

automatically determines the best layout for the volume!

;nless there is a reason to implement a particular layout,

it is best to let vxassist create the layout for each

volume! Gecause the advantaes of the ne# layouts are




related to the size of the volume, vxassist creates the sim-

plest confiuration for smaller volumes and the more complex

stripe-mirror for larer volumes!

The attributes stripe-mirror-col-trier-pt and stripe-

mirror-col-split-trier-pt control the selection! They can

be set in 4etc4default4vxassist! &olumes that are smaller

than stripe-mirror-col-trier-pt are created as mirror-

stripe, and volumes that are larer are created as stripe-

mirror! If vxassist creates the stripe-mirror and the

columns are larer than stripe-mirror-col-split-trier-pt,

the individual subdisks are mirrored instead of mirrorin

the columns of the stripe! Gy default, both of these attri-

butes are set to one iabyte!

The disk roup must be created on a =!@ or later release to

use the ne# layouts, but older disk roups can be updated!

(ee the vxd uprade command for more information on uprad-

in disk roups!

Defined layout specifications are/

concat-mirror

(pecifies that ne# volumes should be concatenated

and mirrored! The mirrorin is handled at each

subdisk level! The attribute stripe-mirror-col-

split-trier-pt is applied!

conti, noconti

Disallo#s or allo#s 0default1 plexes, reular

stripe columns, or RAID-5 stripe columns from

usin multiple reions of disk! If conti is

specified, then plexes and columns must be allo-

cated from a sinle contiuous reion of disk! If

this is not possible, the allocation fails! Gy

default, vxassist tries to allocate space contiu-

ously, but it can use multiple reions or multiple

disks if reuired!

diskalin, nodiskalin

Alins 0default for all volumes except layered

&x&' =!5 +ast chane/ : Mun <@@< =5





volumes1 or does not alin subdisks on cylinder

boundaries! "hen alinment is not disabled, sub-

disks are created beinnin on cylinder boundaries

and are extended to match the end of a cylinder!

Dirty reion lo subdisks, ho#ever, are not

cylinder alined 0they are usually only < or =

blocks lon1! Instead, #hen creatin lo subdisks,

spaces are located from the available disks that

could not be turned into reular subdisks because

the spaces are not cylinder alined! 2or example,

once one cylinder is used for a lo subdisk, that

cylinder cannot be used to create an alined data

0or RAID-5 lo1 subdisk, so other lo subdisks are

created there until that cylinder fills up!

ote/ The diskalin attribute is not supported for

layered volumes 0concat-mirror and stripe-mirror1!

ro#, noro#

Allo#s a volume to ro# durin a relayout opera-

tion!

lo, nolo

Creates 0or does not create1 dirty reion los

0for mirrored volumes1 or lo plexes 0for RAID-5

volumes1 #hen creatin a ne# volume! This attri-

bute can be specified independently for mirrored

and RAID-5 volumes #ith the raid5lo and reionlo

layout specifications! The current implementation

does not support the creation of DC' los in the

layout specification!

mirror, nomirror

(pecifies that ne# volumes should be mirrored or

unmirrored 0default1 respectively! 2or mirror,

the attributes stripe-mirror-col-trier-pt and

stripe-mirror-col-split-trier-pt are applied!

mirror-concat

(pecifies that ne# volumes should be mirrored!

The mirrorin is done at the volume level! The

attributes stripe-mirror-col-trier-pt and

stripe-mirror-col-split-trier-pt are inored

#ith this layout!

mirror-stripe




(pecifies that ne# volumes should be mirrored and

striped! The mirrorin is done at the volume

level! The attributes stripe-mirror-col-trier-pt

and stripe-mirror-col-split-trier-pt are inored

#ith this layout!

&x&' =!5 +ast chane/ : Mun <@@< =B


raid5 (pecifies that ne# volumes should be RAID-5!

raid5lo, noraid5lo

Creates 0default1 or does not create lo plexes

for RAID-5 volumes!

reionlo, noreionlo

Creates or does not create 0default1 dirty-reion

lo subdisks for mirrored volumes!

shrink, noshrink

Allo#s or disallo#s shrinkin of a volume durin a

relayout operation!

span, nospan

Allo#s 0default1 or disallo#s plexes, reular

stripe columns, or RAID-5 stripe columns from

spannin multiple disks! If nospan is indicated,

then plexes or columns can be formed from multiple

reions of the same disk, but cannot be formed

from more than one disk!

stripe, nostripe

(pecifies that ne# plexes should be striped or

unstriped, respectively! "hen creatin a ne#

volume, the default is nostripe! "hen addin a ne#

plex to an existin volume, the default is stripe

if the volume already has one or more striped

plexes, and nostripe in other cases! 2or stripe

0#hen combined #ith mirror, the attributes

stripe-mirror-col-trier-pt and stripe-mirror-

col-split-trier-pt are applied!

stripe-mirror

(pecifies that ne# volumes should be striped and

mirrored! The mirrorin is handled at each column






vxassist -o ordered make strmirvol :@ layout7stripe-mirror S

nstripe7< disk@: disk@< disk@= disk@>

This command mirrors column : across disk@: and disk@=, and

column < across disk@< and disk@>!

The colEs#itch attribute can additionally be used to specify

ho# space on the disks is to be concatenated into columns!

2or example, the follo#in command creates a mirrored-stripe

volume #ith < columns/

vxassist -o ordered make strmir<vol :@ layout7mirror-stripe S

nstripe7< colEs#itch7=,< disk@: disk@< disk@= disk@> S

disk@5 disk@B disk@ disk@N

This command allocates = iabytes from disk@: and < ia-

bytes from disk@< to column :, and = iabytes from disk@=

and < iabytes from disk@> to column <! The mirrors of

these columns are then similarly formed from disks disk@5

throuh disk@N!

&x&' =!5 +ast chane/ : Mun <@@< =N


$ther storae specification classes for controllers, enclo-

sures, tarets and trays can be used #ith ordered alloca-

tion! 2or example, the follo#in command creates a =-column

mirrored-stripe volume bet#een specified controllers/

vxassist -o ordered make mirstr<vol :@ layout7mirror-stripe S

nstripe7= ctlr/c: ctlr/c< ctlr/c= ctlr/c> ctlr/c5 ctlr/cB

This command allocates space for column : from disks on con-

troller c:, for column < from disks on controller c<, and so

on!

;sin (A (torae Attributes #ith vxassist

ote/ This feature of vxassist is desined to #ork in con-

.unction #ith &)RITA( (A%oint Control <!@ and (A Access

+ayer 0(A+1!

The vxassist utility understands storae roups that you

have defined usin &)RITA( (A%oint Control! vxassist sup-

ports a simple lanuae that you can use to specify ho#

disks are to be allocated from pre-defined storae roups!




This specification lanuae defines the confinement and

separation criteria that vxassist applies to the available

storae to choose disks for creatin, resizin or movin a

volume!

The storae specification lanuae consists of set defini-

tions that are used to match a set of disks based on one or

more attribute values!

ote/ *ou cannot use storae specification attributes or the

alloc and #antalloc attributes in combination #ith these (A

storae set specifications!

The simplest form of set definition consists of an operator

and one or more attribute-value pairs, as sho#n here/

operator/attribute7value?,attribute7value!!!

ote/ Attribute-value pairs may be separated by commas or by

spaces! The syntax statements and examples sho#n here use

commas!

(et definitions may be combined into complex clauses #here

an operator is used to combine t#o or more simple set defin-

itions, as follo#s/

operator



!!!

&x&' =!5 +ast chane/ : Mun <@@< =H


U

ote/ (imple set definitions #ithin complex clauses must be

separated by semi-colons if not entered on separate lines!

The operator defines ho# vxassist allocates storae from

disks that match the specified set definition! The follo#-

in operators may be used/

confine Allocate storae only from disks that match all

the specified attribute values!




select Allocate storae from disks that match any of the

specified attribute values!

noneof )xclude disks from bein allocated that match any

of the specified attribute values!

The attributes that can be specified include vendor, loca-

tion, storae account, and protection, type, or luntype!

If reuired, you can use the vxspcsho# command to discover

the device names of disks that have a specified set of

attributes, or to list the attributes of specified disks!

(ee the vxspcsho#0:'1 manual pae for more information!

Command +ine ;sae

A simple set definition consistin of a sinle operator may

be specified as a command line arument to vxassist! The

follo#in example creates a volume usin any combination of

)'C and 9ITAC9I disks that are in disk roup d:/

vxassist - d: make vol: :@@m S

select/vendor79ITAC9I,vendor7)'C

The next example creates a volume usin 9ITAC9I disks of

protection type Raid5 that are in disk roup d</

vxassist - d< make vol< :@@m S

confine/protection7Raid5,vendor79ITAC9I

The final example creates a volume on 9ITAC9I disks, and

mirrors it across the locations buildin: and buildin</

vxassist - d: make vol :@@m mirror7location S

select/vendor79ITAC9I,location7buildin:,location7buildin<

(et Definition Template 2ile

If complex clauses are reuired to define set definitions,

&x&' =!5 +ast chane/ : Mun <@@< >@


these must be placed in a template file! This file contain a

sinle complex or simple set definition! ;se the -) option

to specify the path name of this file to vxassist as sho#n




in this example/

vxassist - d: -) storae!def make vol= :@@m

2or example, the follo#in complex set definition allo#s

storae to be allocated from any combination of disks at

locations loc: and loc</

confine

select/location7loc:

select/location7loc<

U

This clause can also be #ritten as follo#s/

confine

select/location7loc: select/location7loc<

U

)xamples of (et Definitions

Allocate storae usin only 9ITAC9I disks/

confine/vendor79ITAC9I

Allocate storae usin only 9ITAC9I disks of protection type

Raid5/

confine/vendor79ITAC9I,protection7Raid5

Allocate storae usin any combination of )'C and 9ITAC9I

disks/

select/vendor7)'C,vendor79ITAC9I

Do not allocate storae on )'C disks/

noneof/vendor7)'C

The follo#in complex clause allocates storae usin any

combination of )'C and 9ITAC9I disks, and any combination of

Raid5 and 'irr< protection/

&x&' =!5 +ast chane/ : Mun <@@< >:





confine

select/vendor7)'C,vendor79ITAC9I

select/protection7Raid5,protection7'irr<

U

(upport for Remote $peration #ith (A+

If the host on #hich you are runnin vxassist is not the

primary (A+ server, or the port used by the (A+ daemon

0sald1 is not the default 0<N@<1, specify the hostname of

the primary (A+ server and the sald port in the file

4etc4default4vxassistEsalEinfo usin the follo#in format/

salEprimary 7 hostname

salEport 7 portEnumber

The follo#in is an example of such a file/

salEprimary 7 chives

salEport 7 :@@:

ote/ If (A+ cannot be contacted by vxassist for any reason

such as authentication failure, link failure and so on, it

issues a #arnin and completes execution normally! o +;

attributes are retrieved from (A+ in such a scenario!

Authentication #ith (A+

The user name to be authenticated by the (A+ primary server

0if reuired1 may be specified usin the salEusername attri-

bute! ;ser names and pass#ords that &x&' is to use #ith (A+

may be specified usin the vxspcsho# command! (ee the

vxspcsho#0:'1 manual pae for more information!

2I+)(

4etc4default4vxassist (ystem default settins file

for vxassist attributes!

)IT C$D)(

The vxassist utility exits #ith a non-zero status if the

attempted operation fails! A non-zero exit code is not a

complete indicator of the problems encountered, but rather

denotes the first condition that prevented further execution

of the utility!

----------------------------------------------------------------------------------------------------------------------------------------

vxtunefs - tune a &x2( file system

(*$%(I(




vxtunefs ?-ps ?-f tunefstab ?-o parameter7value

?mountEpoint L blockEspecialU!!!

A&AI+AGI+IT*

&RT(vxfs

D)(CRI%TI$

vxtunefs sets or prints tunable I4$ parameters of mounted

file systems! vxtunefs can set parameters describin the

I4$ properties of the underlyin device, parameters to indi-

cate #hen to treat an I4$ as direct I4$, or parameters to

control the extent allocation policy for the specified file

system!

"ith no options specified, vxtunefs prints the existin &x2(

parameters for the specified file systems!

vxtunefs #orks on a list of mount points specified on the

command line, or all the mounted file systems listed in the

tunefstab file! The default tunefstab file is

4etc4vx4tunefstab! *ou can chane the default by settin

the &T;)2(TAG environment variable!

vxtunefs can be run at any time on a mounted file system,

and all parameter chanes take immediate effect! %arameters

specified on the command line override parameters listed in

the tunefstab file!

If 4etc4vx4tunefstab exists, the &x2(-specific mount command

invokes vxtunefs to set device parameters from

4etc4vx4tunefstab! If the file system is built on a &)RITA(

&olume 'anaer 0&x&'1 volume, the &x2(-specific mount com-

mand interacts #ith &x&' to obtain default values for the

tunables, so you need to specify tunables for &x&' devices

only to chane the defaults!

$nly a privileed user can run vxtunefs!

$T)(

vxtunefs #orks #ith (torae Checkpoints ho#ever, &x2( tun-

ables apply to an entire file system! Therefore tunables

affect not only the primary fileset, but also any (torae

Checkpoint filesets #ithin that file system!

The tunables readEunitEio and #riteEunitEio are not sup-

ported!








2or file systems #ith many lare files, the N6 indirect

extent size is too small! The files that et into

indirect extents use a lot of smaller extents instead

of a fe# larer ones! Gy usin this parameter, the

default indirect extent size can be increased so that

lare files in indirects use fe#er larer extents!

Ge careful usin this tunable! If it is too lare, then

#rites fail #hen they are unable to allocate extents of

the indirect extent size to a file! In eneral, the

fe#er and the larer the files on a file system, the

larer defaultEindirEsize can be! The value of this

parameter is enerally a multiple of the readEprefEio

parameter!

This tunable does not apply to disk layout &ersion >!

discoveredEdirectEiosz

Any file I4$ reuests larer than the

discoveredEdirectEiosz are handled as discovered direct

I4$! A discovered direct I4$ is unbuffered like direct

I4$, but it does not reuire a synchronous commit of

&x2( =!5 +ast chane/ @ Mun <@@< =

'aintenance Commands vxtunefs0:'1

the inode #hen the file is extended or blocks are allo-

cated! 2or larer I4$ reuests, the C%; time for copy-

in the data into the pae cache and the cost of usin

memory to buffer the I4$ becomes more expensive than

the cost of doin the disk I4$! 2or these I4$

reuests, usin discovered direct I4$ is more efficient

than reular I4$! The default value of this parameter

is <5B6!

hsmE#riteEprealloc

2or a file manaed by a hierarchical storae manaement

09('1 application, hsmE#riteEprealloc preallocates disk

blocks before data is mirated back into the file sys-

tem! An 9(' application usually mirates the data back

throuh a series of #rites to the file, each of #hich

allocates a fe# blocks! Gy settin hsmE#riteEprealloc

0hsmE#riteEprealloc7:1, a sufficient number of disk

blocks #ill be allocated on the first #rite to the

empty file so that no disk block allocation is reuired




for subseuent #rites, #hich improves the #rite perfor-

mance durin miration!

The hsmE#riteEprealloc parameter is implemented outside

of the D'A%I specification, and its usae has limita-

tions dependin on ho# the space #ithin an 9(' con-

trolled file is manaed! It is advisable to use

hsmE#riteEprealloc only #hen recommended by the 9('

application controllin the file system!

initialEextentEsize

Chanes the default size of the initial extent!

&x2( determines, based on the first #rite to a ne#

file, the size of the first extent to allocate to the

file! Typically the first extent is the smallest po#er

of < that is larer than the size of the first #rite!

If that po#er of < is less than N6, the first extent

allocated is N6! After the initial extent, the file

system increases the size of subseuent extents 0see

maxEseioEextentEsize1 #ith each allocation!

Gecause most applications #rite to files usin a buffer

size of N6 or less, the increasin extents start dou-

blin from a small initial extent! initialEextentEsize

chanes the default initial extent size to a larer

value, so the doublin policy starts from a much larer

initial size, and the file system #on3t allocate a set

of small extents at the start of file!

;se this parameter only on file systems that have a

very lare averae file size! $n such file systems,

there are fe#er extents per file and less

&x2( =!5 +ast chane/ @ Mun <@@< >


framentation!

initialEextentEsize is measured in file system blocks!

maxEbufEdataEsize

ot available!

maxEdirectEiosz




'aximum size of a direct I4$ reuest issued by the file

system! If there is a larer I4$ reuest, it is broken

up into maxEdirectEiosz chunks! This parameter defines

ho# much memory an I4$ reuest can lock at once do not

set it to more than <@W of memory!

maxEdisk

(pecifies the maximum disk ueue enerated by a sinle

file! If the number of dirty paes in the disk ueue

exceeds this limit, the file system prevents #ritin

more data to disk until the amount of data decreases!

The default value is : meabyte!

Althouh it does not limit the actual disk ueue,

maxEdisk prevents processes that flush data to disk,

such as fsync, from makin the system unresponsive!

(ee the #riteEthrottle description for more information

on paes and system memory!

maxEseioEextentEsize

Increases or decreases the maximum size of an extent!

"hen the file system is follo#in its default alloca-

tion policy for seuential #rites to a file, it allo-

cates an initial extent that is lare enouh for the

first #rite to the file! "hen additional extents are

allocated, they are proressively larer 0the alorithm

tries to double the size of the file #ith each ne#

extent1, so each extent can hold several #rites #orth

of data! This reduces the total number of extents in

anticipation of continued seuential #rites! "hen there

are no more #rites to the file, unused space is freed

for other files to use!

In eneral, this allocation stops increasin the size

of extents at <@>N blocks, #hich prevents one file from

holdin too much unused space!

maxEseioEextentEsize is measured in file system

blocks!

ioEcacheEenable

)nables or disables cachin on Xuick I4$ for Databases

files! The default behavior is to disable cachin! To

&x2( =!5 +ast chane/ @ Mun <@@< 5






default value for readEnstream is :!

readEprefEio

The preferred read reuest size! The file system uses

this in con.unction #ith the readEnstream value to

determine ho# much data to read ahead! The default

value is B>6!

#riteEnstream

&x2( =!5 +ast chane/ @ Mun <@@< B


The number of parallel #rite reuests of size

#riteEprefEio to have outstandin at one time! The

file system uses the product of #riteEnstream and

#riteEprefEio to determine #hen to do flush behind on

#rites! The default value for #riteEnstream is :!

#riteEprefEio

The preferred #rite reuest size! The file system uses

this in con.unction #ith the #riteEnstream value to

determine ho# to do flush behind on #rites! The

default value is B>6!

#riteEthrottle

"hen data is #ritten to a file throuh buffered #rites,

the file system updates only the in-memory imae of the

file, creatin #hat are referred to as dirty paes!

Dirty paes are cleaned #hen the the file system later

#rites the data in these paes to disk! 0ote that

data can be lost if the system crashes before dirty

paes are #ritten to disk!1

e#er model computer systems typically have more

memory! The more physical memory a system has, the

more dirty paes the file system can enerate before

havin to #rite the paes to disk to free up memory!

(o more dirty paes can potentially lead to loner

return times for operations that #rite dirty paes to

disk such as sync and fsync! If your system has a com-

bination of a slo# storae device and a lare amount of

memory, the sync operations may take lon enouh to

complete that it ives the appearance of a hun system!




If your system is exhibitin this behavior, you can

chane the value of #riteEthrottle! #riteEthrottle

lets you lo#er the number of dirty paes per file that

the file system #ill enerate before #ritin them to

disk! After the number of dirty paes for a file

reaches the #riteEthrottle threshold, the file system

starts flushin paes to disk even if free memory is

still available! Dependin on the speed of the storae

device, user #rite performance may suffer, but the

number of dirty paes is limited, so sync operations

#ill complete much faster!

The default value of #riteEthrottle is zero! The

default value places no limit on the number of dirty

paes per file! This typically enerates a lare

number of dirty paes, but maintains fast #rites! If

#riteEthrottle is non-zero, &x2( limits the number of

dirty paes per file to #riteEthrottle paes In some

cases, #riteEthrottle may delay #rite reuests! 2or

example, lo#erin the value of #riteEthrottle may

&x2( =!5 +ast chane/ @ Mun <@@<


increase the file disk ueue to the maxEdisk value,

delayin user #rites until the disk ueue decreases!

(o unless the system has a combination of lare physi-

cal memory and slo# storae devices, it is advisable

not to chane the value of #riteEthrottle!

&)RITA( &olume 'anaer 'aximum I4$ (ize

"hen usin stripin on &x&' volumes, to optimize perfor-

mance, the file system issues I4$ reuests that are up to a

full stripe in size! If the volume stripe size is larer

than <5B6, &x&' 0by default1 breaks up the I4$ reuests! To

avoid undesirable I4$ breakup, you can increase the value of

the volEmaxio parameter!

The value of volEmaxio determines the larest amount of

memory that an I4$ reuest can reserve! The recommended

maximum is <@W of the smaller of physical memory or kernel

virtual memory! It is not advisable to o over this limit!

"ithin this limit, you can enerally obtain the best results

by settin volEmaxio to the size of the larest volume

stripe! This applies to both RAID-@ stripin and RAID-5




stripin!

To chane the value of volEmaxio, add an entry to

4etc4system and reboot for the chane to take effect! The

follo#in example sets the maximum I4$ size to :B 'G! ote

that volEmaxio oes after the forceload entry!

forceload/ drv4vxio

set vxio/volEmaxio7=<BN

The value of volEmaxio is in 5:<-byte sectors and is stored

as a :B-bit number, so it cannot be larer than B55=5!

----------------------------------------------------------------------------------------------------------------------------------------

The follo#in examples verify a feature defined for the same

product! The first example identifies the product by its

license key, the second by its product name, and the third

by its product ID!

vxlictest -k %RBB-"%GD-YC*-%=Y%-C%$% -f K&x&'K

vxlictest -n K&)RITA( &olume 'anaerK -f K&x&'K

vxlictest -i N -f K&x&'K

The follo#in example uses uiet mode 0the - can also be

entered as the first arument1/

vxlictest -k %RBB-"%GD-YC*-%=Y%-C%$% -f K&x&'K -

The follo#in example displays all the licensed features in

any keys installed for &olume 'anaer/

vxlictest -n K&)RITA( &olume 'anaerK -l

The follo#in example displays all the licensed features in

the specified key/

vxlictest -k %RBB-"%GD-YC*-%=Y%-C%$% -l

----------------------------------------------------------------------------------------------------------------------------------------

lo - &)RITA( Xuick+o device driver

AVA!LA1!L!. &RT(vxfs

&ES'!P!(" : The &)RITA( Xuick+o device driver is a performance enhance- ment feature for the&)RITA( 2ile (ystem 0&x2(1! Xuick+o improves file system performance by movin all loin of filesystem data and metadata to a separate ra# disk or &x&' volume! This saves disk access time for lo#rites because it eliminates seek time from the loin area to the file system area on a sinle volume or disk! There is no disk seek time involved in the lo #rites on the Xuick+o device, because all lo #rites on

the Xuick-+o device are seuential!




A Xuick+o device is a device file to #hich you can attach up to four Xuick+o &olumes! The volumesprovide the disk space for the file systems bein loed to that device! The Xuick+o devices are named /

o 4dev4lo4admin

o 4dev4lo4vxlo:-=:

o 4dev4lo4cvxlo:-=<

The admin device is for Xuick+o internal use! The =: 4dev4lo4vxlo:-=: devices are for loin local filesystems! The =< 4dev4lo4cvxlo:-=< devices are for loin clustered file systems!

2or Xuick+o to lo &x2( file system data and metadata 0referred to as enablin Xuick+o for a filesystem1, all &x2( lo #rites are redirected from the &x2( intent lo to a Xuick+o device!

Another key aspect of Xuick+o is crash recovery! Durin a system start up, the Xuick+o startup script,4etc4rc(!d4(NNlo-startup, searches the Xuick+o confiuration file 0see loEconfi0>11! 2or eachXuick+o device in this file that is in the attached state, the script tries to recover the lo data and metadatathat #ere not committed to the &x2( file system before the crash or reboot 0see lock0:'11! If this data issuccessfully recovered, &x2( does not need to perform a full consistency check #hen runnin fsck! If anerror occurs on one of the &x2( file systems, only that file system #ith the error has a full consistencycheck run! The confiuration information for cluster Xuick+o devices is maintained internally, not in theXuick+o confiuration file 04etc4lo4confi1, and is consistent across the cluster!

If an error occurs on one of the Xuick+o devices or Xuick-+o volumes, the Xuick+o device is removedand a full consistency check is performed on the &x2( file systems that #ere enabled on this device!2inally, all recovered Xuick-+o volumes are reattached to Xuick+o devices and are ready to beinloin after the &x2( file systems are mounted!

To bein loin a &x2( file system by a Xuick+o device, there are a fe# set up steps! 2irst, the&RT(vxfs packae must be installed! This modifies the 4etc4devlink!tab file and creates the B= Xuick+odevice nodes that can be used to attach Xuick+o volumes to the Xuick+o driver! Then choose the &x2(file systems are to be enabled on these Xuick+o devices! 2or each of these file systems, the ta lo7must be added to the mount option field of its entry in the 4etc4vfstab file as in the follo#in example/

Q device device mount 2( fsck mount mount

Q to mount to fsck point type pass at boot options

4dev4vx4dsk4vol: 4dev4vx4rdsk4vol: 4vol: vxfs : no lo7

At this point, there are t#o methods of enablin Xuick+o on a file system! $ne #ay is to remount the&x2( file system #ith the modified entry in 4etc4vfstab! This can be done by runnin mount -o remount! Theother method is to run loenable on a mounted file system3s mount point! loenable incorporates mount-o remount,lo7! and issues the mount system call! (imilarly, to disable loin by Xuick+o #ithoutunmountin the &x2( file system across system reboots, remove the lo7 option from the 4etc4vfstab fileand run mount -o remount! *ou can also run the lodisable command!

The Xuick+o confiuration file is 4etc4lo4confi!

Xuick+o can use &x&' or ra# disk partitions for all Xuick-+o volumes! A cluster Xuick+o device mustuse a shared Cluster &olume 'anaer 0C&'1 volume for Xuick+o volumes! &x2( can operateindependently from Xuick+o!

'luster *ile S$stem !ssues : This section describes the operation of Xuick+o on cluster file systems!

'luster DuickLog &evices There are up to =< Xuick+o device nodes in a cluster! All the systems in a

cluster can access a cluster Xuick+o device, but a iven Xuick+o device can be accessed by only onesystem at a time! The cluster node that has access to the Xuick+o device is termed the master! Thecluster Xuick+o device master mediates all lo transactions for the cluster, and only the master canchane the cluster confiuration information! 'ost Xuick+o commands master the device automatically,and no manual intervention is reuired! If a non-master node tries to initiate a confiuration update, thecorrespondin ioctl returns an )G;(* dianostic!

The confiuration information for all the cluster Xuick+o devices is duplicated on all nodes! Thisinformation is kept consistent by broadcastin any confiuration updates! "hen a node .oins a cluster, itreceives the confiuration information from one of the existin member nodes! The confiurationinformation is used primarily durin a cluster reconfiuration!

"hen a master node leaves the cluster, all the other nodes in the cluster mark the master node devicesKDIRT*!K "hen a file system check 0fsck1 is run on a file system, the cluster Xuick+o confiurationinformation is checked to determine if the file system #as enabled to a cluster Xuick+o device! If so, the

cluster Xuick+o device is recovered before the fsck command does a lo replay! If the primary file systemis Xuick+o enabled and leaves the cluster, the secondary file system that assumes the primaryship can beenabled to a different cluster Xuick+o device! 2or each shared diskroup in a cluster, it is advisable to




confiure either one cluster Xuick+o device per cluster file system, or one per node, #hichever number issmaller!

'luster DuickLog &evice Life '$cle

'LEA" Initial state of the device! The device is clean and there are no &x2( file systems enabled by it!

&!. The master node of the cluster Xuick+o device has left the cluster! In this state, no node can use

the device! $nly a C+)A or R)C$&)R)D device can be used for loin!E'(VEE& The DIRT* cluster Xuick+o device #as recovered! The device is clean and there are no&x2( file systems enabled by it!

2"&EE'(VE. The DIRT* cluster Xuick+o device is bein recovered!

E(S The Xuick+o driver returns the standard error codes!

2I+)(

4dev4lo4admin The Xuick+o device driver special device node reserved solely for administrativepurposes!

4dev4lo4vxlo ?:-=: The Xuick+o device driver special device nodes used for &x2( file system loin!

4dev4lo4cvxlo ?:-=< The Xuick+o device driver special device nodes used for &x2( file system loin!These are the cluster Xuick+o devices!

4etc4lo4confi Xuick+o confiuration file!4etc4rc(!d4(NNlo-startup Xuick+o start up script!

4etc4vfstab Table of file system default parameters!

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------




----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------------------

Documents

Commands Veritas