|
|
vxvm problem in redhat 5.4
06-29-2011
|
|
vxresize(1M) vxresize(1M) NAME
vxresize - change the length of a volume containing a file system SYNOPSIS
/etc/vx/bin/vxresize [-bfnsx] [-F fstype] [-g diskgroup] [-o {override|verify}] [-t tasktag] volume new_length [[!]medianame...] [specification_arguments] DESCRIPTION
The vxresize command either grows or shrinks both the file system and its underlying volume to match the specified new volume length. The ability to grow or shrink is file system dependent. Some file system types may require that the file system be unmounted for the operation to succeed, as shown in the following table: ______________________________________________________________ | | Online JFS | Base JFS | HFS | | | (Full-VxFS) | (Lite-VxFS) | | |______________|_______________|_______________|_______________| | Mounted FS |Grow and shrink| Not allowed | Not allowed | | | (uses fsadm) | | | |______________|_______________|_______________|_______________| | Unmounted FS | Grow only | Grow only | Grow only | | |(uses extendfs)|(uses extendfs)|(uses extendfs)| |______________|_______________|_______________|_______________| Note: o vxresize works with JFS (derived from Veritas File System (VxFS)) and HFS file systems only. o In some situations, when resizing large volumes, vxresize may take a long time to complete. o Resizing a volume with a usage type other than FSGEN or RAID5 can result in loss of data. Use the -f option to force resizing of such a volume. o You cannot resize volumes comprised of different layout types. If you try to do so, an error message displays stating that the volume contains a different organization. The new_length operand can begin with a plus (+) or minus (-) to indicate that the new length is added to or subtracted from from the cur- rent volume length. Specify the new length, or change in length, in Veritas Volume Manager standard length units (see vxintro(1M)). The vxresize command accepts the Intelligent Storage Provisioning (ISP) storage specification arguments that are used with the vxassist command, and other vxassist specification arguments such as mirror, stripe and alloc if the volume is not an ISP volume. The arguments are passed unmodified to the vxassist command. For example, medianame operands can be specified to name the disks that are to be used for allocating new space for a volume. These argu- ments can be a simple name for a disk media record, or they can be of the form medianame, offset to specify an offset within the named disk. If an offset is specified, then regions from that offset to the end of the disk are considered candidates for allocation. If a medianame operand is prefixed by !, the specified storage is excluded from the allocation process. See the vxassist(1M) manual page for information about storage specification arguments. OPTIONS
-b Performs the resize operation in the background. The command returns quickly, but the resize will be in progress. Use the vxprint command to determine when the operation completes. Note: This option is only honored for grow operations on non-RAID5 volumes. Otherwise, it is ignored. -f Forces a operation that is usually disallowed by vxresize. -F fstype Supplies the type of the file system to be resized. -g diskgroup Limits operation of the command to the given disk group, as specified by disk group ID or disk group name. The volume operand is evaluated relative to the given disk group. -n Prevents resizing of a volume if it does not contain a file system. -s Requires that the operation represent a decrease in the volume length. -t tasktag If any tasks are registered to track the progress of the operation, mark them with the tag tasktag. The tag specified by tasktag is a sequence of up to 16 alphanumeric characters. -x Requires that the operation represent an increase in the volume length. Fail the operation otherwise. Hardware-Specific Options Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when creating volumes or allocating space for volumes. By default, vxresize only resizes volumes such that the vol- umes conform with these guidelines. The following options change the behavior of vxresize: -o override Resizes the specified volume and ignores any storage-specific guidelines. Overriding the guidelines is not recommended as it can result in incompatible objects, or objects that cannot be administered by VxVM and any associated software that exploit storage- specific features. -o verify Verifies that the specified volume can be resized without violating any storage-specific guidelines, but does not resize the vol- ume. If any guidelines are violated, vxresize exits with an error message. Note: These options need a specific license. Without the license, vxresize ignores the specified option. NOTES
When a non-ISP volume is grown, its layout may be converted as a side effect if vxassist determines that the new volume is too large for the original layout. The values of the stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt attributes (by default, 1 giga- byte) control whether a new layout will be applied. A mirror-stripe volume that is larger than the value of stripe-mirror-col-trigger-pt is converted to a stripe-mirror volume. If each column of a stripe-mirror-col volume is larger than the value of stripe-mirror-col-split- trigger-pt, the volume is converted to a stripe-mirror-sd volume where the individual subdisks, rather than the columns, are mirrored. A mirror-concat volume that is larger than the value of stripe-mirror-col-split-trigger-pt is converted to a concat-mirror volume where the individual subdisks, rather than the plexes, are mirrored. When a non-ISP volume is shrunk, its layout may be converted as a side effect if vxassist determines that the new volume is too small for the original layout. The values of the stripe-mirror-col-trigger-pt and stripe-mirror-col-split-trigger-pt attributes (by default, 1 giga- byte) control whether a new layout will be applied. A stripe-mirror volume that is smaller than the value of stripe-mirror-col-trigger-pt is converted to a mirror-stripe volume. A concat-mirror volume that is smaller than the value of stripe-mirror-col-split-trigger-pt is converted to a mirror-concat volume. If the new layout of a non-ISP volume is inappropriate, use the vxassist convert operation to change the layout after the grow or shrink operation has finished. For a CFS file system, the vxresize command must be executed on the CVM master node (as indicated by vxdctl -c mode), which must also be the CFS primary (as indicated by fsclustadm -v showprimary mount_point). If the master node is not the same node as the CFS primary, you can grow a CFS file system by running the vxassist growto or growby command on the CVM master node, followed by the fsadm -b command on any CFS node. To shrink a CFS file system, run the fsadm -b command on any CFS node, and then run the vxassist shrinkto or shrinkby command on the CVM master node. It is not possible to resize a component volume of a volume set that has an unmounted file system. This is because the extendfs command is not supported for volume sets with unmounted file systems. SEE ALSO
extendfs_vxfs(1M), fsadm_vxfs(1M), vxassist(1M), vxintro(1M), vxprint(1M), vxtask(1M) Veritas Volume Manager Administrator's Guide Veritas Storage Foundation Intelligent Storage Provisioning Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxresize(1M)