{"id":181,"date":"2009-12-31T17:11:05","date_gmt":"2009-12-31T09:11:05","guid":{"rendered":"http:\/\/www.sysadmindayph.com\/blog\/?p=181"},"modified":"2009-12-31T17:11:43","modified_gmt":"2009-12-31T09:11:43","slug":"veritas-volume-manager-vxvm-basics-commands-cheats","status":"publish","type":"post","link":"https:\/\/www.sysadmindayph.com\/blog\/veritas-volume-manager-vxvm-basics-commands-cheats\/","title":{"rendered":"Veritas Volume Manager VxVM Basics Commands Cheats"},"content":{"rendered":"

Veritas Volume Manager VxVM Basics Commands Cheats<\/a>.. The authority site for this topic, the VXVM on VXFS, if you do a Google search for any tutorial or command cheat sheet is Cuddletech.<\/p>\n

I want to post… say, borrowing, the content of that page to this post for my own personal reference… Love your own page right? And since I am more likely to open SysadminPH that cuddletech, I thought we not copy the Veritas tutorial page here for my ease of access?<\/p>\n

<\/p>\n

The Cuddletech Veritas Cheat Sheet<\/p>\n

\t\tby: B. Rockwood
\n\t benr@cuddletech.com<\/p>\n

Overview:
\n——–<\/p>\n

The purpose of this paper is to
\nquickly get you up to speed in Veritas,
\nand to act as a quick referance. All new
\nusers to Veritas are HIGHLY encouraged to
\nfirst read the Veritas users guides enlucded
\nwith Veritas, and found on docs.sun.com<\/p>\n

Remember!: Almost all commands can use several
\n diffrent options that are similar
\n across all commands. The most used
\n of these is “-g ” which
\n specifies which Disk Group the command
\n will be executed on. For instance,
\n vxinfo will only display volume information
\n for volumes in the rootdg, to see
\n volumes in the datadg, for instance, use:
\n Ex: “vxinfo -g datadg”<\/p>\n

———————————————–
\n DISPLAY and MONITORING
\n———————————————–<\/p>\n

vxdisk list
\n List all disks used by Veritas (VX).<\/p>\n

vxdisk list
\n Display detailed information about a
\n single disk, including mutlipathing
\n information, size, type, Vx version,
\n and more.<\/p>\n

vxprint
\n Display report style information about
\n the current status of all Vx componants,
\n including disks, subdisks, plexes, and
\n volumes.<\/p>\n

vxprint
\n Display report style information about
\n the current status of ONLY the componant
\n you request. So for instance,
\n “vxprint vol01” shows information about
\n all subcomponants of vol01. This works
\n for plexes, disk groups, etc.<\/p>\n

vxprint -hrt
\n\tDisplay detailed information about all
\n\tVx componanats, including stwdith,
\n\tncolumns, offsets, layout type, read-
\n\tpolicy, and more. This is best for
\n\ta true picture of your configuration.<\/p>\n

vxdg list
\n Display listing and state information
\n of all Disk Groups.<\/p>\n

vxdg list
\n Display detailed information about
\n a diskgroup, including flags, version,
\n logs status, etc.<\/p>\n

vxinfo
\n Display volume status and volume type.
\n By default, only displays “rootdg”,
\n to display a diffrent Disk Group,
\n use “vxinfo -g “.<\/p>\n

vxassist maxgrow
\n This command will output the maximum size
\n the volume specified can increased by,
\n specified in sectors.<\/p>\n

————————————————–
\n DISK TASKS and COMMANDS
\n————————————————–<\/p>\n

vxdiskadd
\n Adds a disk to Vx by Initializing and Encapsolating
\n it. Specified by its device name (ex: c0t1d0s2).
\n NOTE: You’ll need to reboot to finalize the
\n disk addition!<\/p>\n

This command, can also be used to add a disk to
\n a specified disk group. Just follow the prompts.
\n No reboots needed for changing DG’s.<\/p>\n

vxedit rename
\n Rename a Vx disk. Ex: “vxedit rename disk01 disk05”<\/p>\n

vxedit set reserve=on
\n Sets the “reserve” flag to a Vx disk. This
\n is used to keep specific disks from being
\n accidentally, or generally used.<\/p>\n

vxdisk offline
\n Used to “offline” a disk. The disk should
\n be removed from its diskgroup before being
\n offlined.<\/p>\n

vxdisk rm
\n Used to remove disks from Vx control completely.
\n Ex: “vxdisk rm c0t1d0s2” Make sure to
\n removed the disk from its diskgroup, and offline
\n the disk before removing it.<\/p>\n

vxedit set spare=on
\n Sets the “spare” flag to a Vx disk. This is used
\n to make the specified disk a hot spare, which
\n is then added to the “hot spare pool”.<\/p>\n

vxedit set spare=off
\n Same as above but removes the disk from the
\n “hot spare pool”.<\/p>\n

—————————————————-
\n DISK GROUPS and COMMANDS
\n—————————————————-<\/p>\n

vxdg init =
\n Creates a new disk group, and assigns the naming
\n scheme to the first disk added to the group.
\n ex: “vxdg init newdg newdg01=c0t10d0s2”.
\n NOTE: This is kinda tricky because the disk that
\n you’re adding can’t be a member of ANY DG, but
\n must be initialized. It’s easier to use
\n “vxdiskadd”, and add the disk to a newdg by
\n specifying a new DG name for the DG field.<\/p>\n

vxdg deport
\n Disabled a diskgroup, but doesn’t remove it. Often
\n used as an organized pool of disk to realocate, and
\n to moved DG’s from one system to another.<\/p>\n

vxdg import
\n Reverse of above. Enables local access to the specified
\n disk group.<\/p>\n

vxdg -n \n Change a Disk Groups name.<\/p>\n

vxdg list
\n Use this to check the version numbers of Disk
\n Groups. Shows other details about the DG too.<\/p>\n

vxdg destroy
\n Removes the specified DG, and frees all its disks
\n back to general use by Vx.<\/p>\n

-= Quick Chart!: Disk Group Version Number Translation<\/p>\n

VxVM Introduced Supported
\n Release Version Versions
\n ——- ———— ———
\n 1.2 10 10
\n 1.3 15 15
\n 2.0 20 20
\n 2.2 30 30
\n 2.3 40 40
\n 2.5 50 50
\n 3.0 60 20-60<\/p>\n

———————————————————–
\n SUBDISKS and COMMANDS
\n———————————————————– <\/p>\n

vxmake sd ,,
\n Creates a subdisk with the specified name,
\n and by the offset and length specified.
\n ex: “vxmake sd disk02-01 disk02,0,8000”
\n NOTE: If you are going to add this subdisk
\n to a plex, its good to check the other
\n subdisks in that plex to see what their
\n lengths and offsets are, use the command:
\n “vxprint -st”<\/p>\n

vxedit rm
\n Removes a subdisk. <\/p>\n

vxsd assoc ,….
\n Associates the specified subdisks to
\n the specified plex. Example:
\n “vxsd assoc vol01-03 disk01-01,disk02-01”
\n NOTE: Striped volumes are diffrent,
\n you need to specify the column# so
\n use the following: <\/p>\n

vxsd -l assoc ,…
\n Same as above, but used for associating
\n\tsubdisks to a striped plex. Use the command
\n “vxprint -st” to see what other subdisk
\n in the plex look like, and then set the
\n new subdisks column number and offset
\n (found in the seventh column of output)
\n to the appropriate value.<\/p>\n

vxsd aslog
\n Adds a log subdisk to the specified plex.
\n Ex: “vxsd aslog vol01-02 disk03-01” <\/p>\n

vxsd dis
\n Disassociates the specified subdisk from its
\n current plex. <\/p>\n

——————————————————
\n PLEXS and COMMANDS
\n——————————————————<\/p>\n

vxmake plex sd=,,….
\n Creates a new plex by the name specified and
\n assigns the specified subdisks to it.<\/p>\n

vxmake plex layout= stwidth= ncolumn= sd=…
\n\tLike above command, but specifies layout type
\n\tas defined by , which is used for creation
\n\tof striped and RAID5 plexes. The layout is
\n\tconstrained by the defined number of columns,
\n\tand stripe width. Subdisks specified are
\n\tadded to the created plex.\t<\/p>\n

vxplex att \n Associates specified plex with specified volume.
\n (Adds a mirror)
\n NOTE: Attachment will take a while. Watch
\n it with Vxtask, or via vxprint<\/p>\n

vxplex dis \n Disassociate specified plex from its connected
\n volume.<\/p>\n

vxedit -r rm \n Remove the plex.<\/p>\n

vxmend off \n Offlines a plex for repair to it’s disks.<\/p>\n

vxplex det \n Detaches specified plex from its connected
\n volume, but maintians association with it’s
\n volume. The plex is no longer used
\n for I\/O untill it is (re)attached.<\/p>\n

vxmend fix clean \n Used to clean plexes that are in the
\n “unclean” state. Used with unstartable
\n volumes.<\/p>\n

vxplex mv
\n Moves the data content from the origonal
\n plex onto a new plex.
\n NOTE: The old plex must be active (ENABLED).
\n The new plex should be the same length, or
\n larger than the old plex. The new plex
\n must not be associated with another volume.
\n (duh)<\/p>\n

vxplex cp
\n Copies the data from the specified volume
\n to a new plex.
\n NOTE: The new plex cannot be associated
\n with any other volume. The new plex,
\n further, will NOT be attached to
\n the specified volume. (Also, see notes
\n from above)<\/p>\n

——————————————————-
\n VOLUMES and COMMANDS
\n——————————————————-<\/p>\n

vxassist make
\n Creates a new volume with the name specified
\n and is made to the length specified.
\n Ex: “vxassist make newvol 10m”
\n NOTE: This command will pull disk space
\n from the generally avalible Vx disk space.<\/p>\n

vxassist make layout= ….
\n Like the above command, but with layout specified.
\n The most common layouts are: striped and raid5
\n ex: “vxassist make newvol 100m layout=raid5 disk01 disk02 disk03”
\n NOTE: See the vxassist(1M) man page for more information.<\/p>\n

vxmake vol len= plex=,…
\n Creates a new volume of specified length (usually
\n in sectors), and attachs the specified plexes to that
\n volume. Useful for creating volumes to house
\n copied or moved plexes.
\n NOTE: See the vxmake(1M) man page for more information.<\/p>\n

vxvol init [plexname]
\n Manually sets the state of a volume.
\n NOTE: Not for the squimish.<\/p>\n

vxassist maxsize [layout=raid5]
\n Returns the maximum size avalible via Vx to create
\n a new volume. By adding “layout=raid5” to the command
\n the calulations take into account losse due
\n to raid5. Output is in sectors and Megs.<\/p>\n

vxassist maxgrow
\n Returns the maximum ammount of Vx space that
\n can be added to the specified volume.<\/p>\n

vxassist mirror
\n Creates a mirror for the specified volume.
\n NOTE: Think of this as “handsfree plex creation”.
\n This is fast, but the disks you want used
\n may not be used… often best to do manually.<\/p>\n

vxassist addlog
\n Adds a Dirty Region Log (DRL) for the specified volume.<\/p>\n

vxassist remove log
\n Reverse of above.<\/p>\n

vxvol start
\n Starts a volume<\/p>\n

vxvol stop
\n Stops a volume. Alternately you can use command as
\n such: “vxvol stopall” in order to stop all volumes.<\/p>\n

vxassit growto\/growby\/shrinkto\/shrinkby
\n Resizes the volume specified. Use one of the
\n following: growto, growby, shrinkto, and shrinkby
\n in order to descide what specifies.
\n By default length is specified in sectors.
\n This does not resize the filesystem inside the volume.
\n NOTE: Don’t shrink volumes to be less that
\n its contained filesystem! (duh)<\/p>\n

vxvol set len=
\n An alternate to above command. Sets the absolute
\n lenths of the specified volume to the length
\n specified, by default, in sectors. This
\n does not resize the filesystem inside the volume.<\/p>\n

NOTE: There is also a resize(1M) command, used
\n for resizing both volume AND filesytem. See
\n the man page for that one.<\/p>\n

vxedit rm
\n Removes the specified volume. (poof!)
\n NOTE: If the volume specified is in the ENABLED
\n state, you will need to use the command
\n “vxedit -f “. Also, using the “r”
\n with “f” will remove all plexes and subdisks
\n with the volume. If you didn’t guess, “r”
\n is Recursive, and “f” is Force.<\/p>\n

—————————————————————-
\nMisc Stuff:<\/p>\n

To calculate the size of a filesystem inside a volume, use
\nthe command:
\n\tfstyp -v | head -30 | grep ncg
\nIgnore the errors. Output will look this this:
\n # fstyp -v \/dev\/vx\/rdsk\/datadg\/vol01 | head -30 | grep ncg
\n ncg 17152 size 70254592 blocks 65863396
\n # Broken Pipe
\n Unknown_fstyp (no matches)
\nThe size found after the label “size” is presented in kilobytes.
\nYou can convert to sectors by multiplying by 2.<\/p>\n

\t\t———–<\/p>\n

To calculate the size of a volume, use vxprint, and look for the
\n“len”. The volume length is in sectors. Convert to kilobytes
\nby dividing by 2.<\/p>\n

\t\t————-<\/p>\n

Volume Growth Procudure:
\n1) You can use vxassist to estimate the max size of
\na given volume based on the disks you wish to add:
\nex: # vxassist -g rootdg maxgrow vol01 disk01 disk02 disk03<\/p>\n

2) Next, actually grow the volume (NOT THE FS) via the
\ncommand (assuming maxgrow outputed 10639360 as the maxsize):
\nex:# vxassist -g rootdg growto vol01 10639360 disk01 disk02 disk03<\/p>\n

3) Now VxVM grinds away, monitor with vxtask.<\/p>\n

4) Now Grow the Filesystem, for UFS use:
\n# \/usr\/lib\/fs\/ufs\/mkfs -F ufs -M \/export \/dev\/vx\/rdsk\/rootdg\/vol01 10639360<\/p>\n

for VXFS ufs:
\n# \/usr\/lib\/fs\/vxfs\/fsadm -b 10639360 -r \/dev\/vx\/rdsk\/rootdg\/vol01 \/mnt
\n—————————————————————<\/p>\n

5) Done!<\/p>\n

\t———-<\/p>\n

Changing User\/Group of a Raw Volume: (ex:)
\n vxedit -g xxxdg set group=dba data_vol_123
\n vxedit -g xxxdg set user=oracle data_vol_123<\/p>\n

Thanks to Ben Rockwood! Cheers!<\/p>\n","protected":false},"excerpt":{"rendered":"

Veritas Volume Manager VxVM Basics Commands Cheats.. The authority site for this topic, the VXVM on VXFS, if you do a Google search for any tutorial or command cheat sheet is Cuddletech. I want to …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16,5,312],"tags":[316,313,391,315,314],"class_list":["post-181","post","type-post","status-publish","format-standard","hentry","category-commands","category-solaris","category-veritas-volume-manager","tag-diskgroups","tag-veritas","tag-veritas-volume-manager","tag-vxfs","tag-vxvm"],"_links":{"self":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/comments?post=181"}],"version-history":[{"count":2,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/181\/revisions"}],"predecessor-version":[{"id":183,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/181\/revisions\/183"}],"wp:attachment":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/media?parent=181"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/categories?post=181"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/tags?post=181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}