Sponsored Content
Full Discussion: vxvm problem in redhat 5.4
Operating Systems Linux Red Hat vxvm problem in redhat 5.4 Post 302534976 by life008 on Wednesday 29th of June 2011 09:26:22 AM
Old 06-29-2011
vxvm problem in redhat 5.4

Hi

I have a problem related to vxvm. I am using redhat5.4 64 bit
vxassist -g mydg growto my-vol 2G (Actually when i am running this command then this command is not increasing the size of volume but this command is running fine and the size which i have given to my volume it has been reduced from disk becoz when i am checking vxassist -g mydg maxsize so 2GB size deduct from group...........Smilie


Kindly help
Jeevan Bhatt
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

<< booting problem with redhat 8.0 >>

i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies

2. UNIX for Dummies Questions & Answers

Linux Redhat 8.0 Problem

can someone tell me what commands in Linux RedHat 8.0 will give me a graph of whats going on on my system. When Is ay graphs I mean graphs like does produced by perfview of solaris and glance of HP-UX. (3 Replies)
Discussion started by: TRUEST
3 Replies

3. Windows & DOS: Issues & Discussions

HELP--Redhat on WinXP laptop PROBLEM!!

Hi guys! Need some help here.....trying to install Redhat 8.0 on a laptop that is already running WinXP. Have made a partition with partition magic but when I try to install Linux it just stops at the check partition/ check hard-drive stage. It has happened on two different laptops of different... (4 Replies)
Discussion started by: syrex
4 Replies

4. UNIX for Dummies Questions & Answers

Display Problem On Linux Redhat 8.0

Hey guys, can anyone please tell me how I can make linux recognize the same video adapter/monitor type that my windows box is using? i'm running linux redhat on virtual PC which enables me to have windows and linux running at the same time. (i can switch back and forth between operating... (4 Replies)
Discussion started by: TRUEST
4 Replies

5. Red Hat

Rsh problem on redhat linux

Hi, I am trying to do rsh on to a redhat EL 5 machine. It repeatedly asks me for the password and die after sometime. One might think that I am giving the wrong password. But I can do 'ssh' on to that machine with the same password. Can someone tell me what I have been doing wrong? ... (2 Replies)
Discussion started by: eamani_sun
2 Replies

6. UNIX for Dummies Questions & Answers

vi problem, sco -> redhat

I rlogin from a sco box to a redhat box and run /bin/vi. Pgup, Pgdn, and arrow up/down keys don't work. I enter "export TERM=ansi80x25" and run vi again.Everything works just like I like it. Except the cursor turns into a blinking overscore. When I exit vi and close the connection to redhat,... (2 Replies)
Discussion started by: bussyw
2 Replies

7. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

8. Red Hat

Help with Redhat installation problem

Hello; I have 4 servers with RedHat Enterprise server 32-bit installed. i'm trying to install 64-bit system instead but the hardware has only CD drive (not DVD). When i tried to use external DVD drive and connect it to the USB to install the 64-bit system, it starts ok but then it ask for the... (2 Replies)
Discussion started by: Katkota
2 Replies

9. Red Hat

Redhat 9 installation problem

All, I am trying to install redhat9 to my system. I have 26 GB of unpartitioned space, and I do have xp-2 already installed on my system in c: . I am using external DVD-RW to install linux. I have booted the CD, chosen Graphical mode and now installation frizzed with below message: ... (5 Replies)
Discussion started by: joshilalit2004
5 Replies

10. Red Hat

Redhat network registration problem

Dear members & admins I have 3 RHEL 5.7 servers. So I decided to upgrade them to latest version. 2 of them successfully upgraded to RHEL 5.11 and last one is the problem. When I hit rhn_register command server shows following info : #rhn_register There was an SSL error: (104, 'Connection... (2 Replies)
Discussion started by: sembii
2 Replies
vxvset(1M)																vxvset(1M)

NAME
vxvset - create and administer volume sets SYNOPSIS
vxvset [-g diskgroup] [-c "ch_addopt"] [-f] [-o index] addvol vset vol [index] vxvset [-g diskgroup] list [vset] vxvset [-g diskgroup] [-t ch_subdir] [-m "ch_initopt"] [-o index] [-o makedev={on|off}] [-o compvol_access={read-only|read-write}] [-c "ch_addopt"] make vset vol [index] vxvset [-g diskgroup] [-f] [-c "ch_rmopt"] [-o index] rmvol vset {vol | index] vxvset [-g diskgroup] [-f] set compvol_access={read-only|read-write} vset vxvset [-g diskgroup] [-f] set makedev={on|off} vset vxvset [-g diskgroup] [-f] start vset ... vxvset [-g diskgroup] [-f] stop vset ... vxvset [-g diskgroup] assoc rvg vset vxvset [-g diskgroup] [-f] dis vset DESCRIPTION
Volume sets in Veritas Volume Manager (VxVM) provide support for the Multi-Volume Support feature that can be used with Veritas File System (VxFS). A volume set allows several volumes to be treated as a single object with one logical I/O interface. The vxvset utility is used to create and administer volume sets. KEYWORDS
addvol Moves the specified standalone volume, vol, into the volume set, vset. If the -o index option is specified, the value of the index argument is assigned to the volume. If the -o index option is not specified, an index value is assigned automatically. Note: If the volume set is associated to the RVG then the added volume is associated to the RVG automatically. Note: The volume must be in the same disk group as the volume set, and it may not already be a member of another volume set. After the move, any ch_addopt argument string that is specified using the -c option is passed to the vset_addvol content-handler operation (if any). This string indicates how the volume is to be processed by the application. For example, the string may indicate how the volume should be incorporated into a file system. The vset_addvol operation may provide a context string that is stored in the volume record. Note: The -f (force) option must be specified if the volume being added, or any volume in the volume set, is either a snapshot or the parent of a snapshot. Using this option can potentially cause inconsistencies in a snapshot hierarchy if any of the volumes involved in the operation is already in a snapshot chain. list If a volume set, vset, is specified, lists the component volume information. This includes the values of the volume name, index in the volume set, length and kernel state of the volume, and the context string for the volume set. If a volume set is not specified, limited information about all volume sets in all disk group is displayed. This includes the volume set name, disk group name, number of volumes in each set, and the context string for the volume. make Creates a new volume set with a name specified by the vset argument and adds the specified volume, vol, to it. If specified, the -t option defines the name of a content-handler subdirectory, ch_subdir, under the directory /usr/lib/vxvm/con- tent. This optional subdirectory contains one or more utilities that support all possible volume-set operations for the inter- face to an application. For example, -t vxfs specifies that the vxfs subdirectory is used for VxFS. Any ch_initopt argument that is specified using the -m option is passed to the vset_initset content handler operation (if any) that deals with volume set initialization. The vset_initset operation may provide a context string that is stored in the volume set record. After adding the first volume to the volume set, any ch_addopt argument that is specified using the -c option is passed to the vset_addvol content-handler operation (if any). This string indicates how the volume is to be processed by the application. For example, the string may indicate how the volume should be incorporated into a file system. The vset_addvol operation may provide a context string that is stored in the volume record. If the -o makedev=on option is specified, raw device nodes are set up for each of the component volumes in the volume set that is being created. If set to off (default), no raw device nodes are created. If the -o compvol_access option is specified in conjunction with the -o makedev=on option, this specifies the degree of access that is allowed to the raw device nodes. If set to read-only (default), only reads are allowed on the raw device of each compo- nent volume of a volume set that is being created. If set to read-write, both reads and writes are allowed. rmvol Removes the specified volume, vol, from the volume set, vset, and makes it available a standalone volume. If the -o index option is specified and an index is provided instead of a volume name, the volume with that index is removed from the volume set. Note: If the volume set and the volume is associated to the RVG then this operation automatically dissociate the volume from the RVG. The content-handler string, ch_rmopt, that is specified by the -c option is passed to the vset_rmvol content-handler operation (if any). Typically, the vset_rmvol operation (if any) may choose to reorganize the data in the data set before performing the remove operation, or alternatively, it may cancel the the remove operation altogether. Note: A volume set is deleted when the final volume is removed from it. Note: The -f (force) option must be specified if the volume being removed, or any volume in the volume set, is either a snapshot or the parent of a snapshot. Using this option can potentially cause inconsistencies in a snapshot hierarchy if any of the vol- umes involved in the operation is already in a snapshot chain. set Sets one of the following attributes on a volume set: compvol_access={read-only|read-write} If set to read-only, only reads are allowed on the raw device of each component volume of a volume set. If set to read-write, both reads and writes are allowed. This attribute only has any effect if the makedev attribute has been enabled for the volume set. If not specified, the default setting is read-only if makedev is set to on. makedev={on|off} If set to on, creates raw device nodes for each of the component volumes in a volume set. If set to off (default), any existing raw device nodes are removed. If any of the component volumes of the volume set is open, the -f option is required to forcibly set the makedev attribute to off or the compvol_access attribute to read-only. start Attempts to start all volumes under the specified volume sets. If a volume would not normally be started because failures and disk removals have left all associated plexes with invalid data, the -f option can be used to try to start the volume. This option can be used after replacing disks to enable the volume. The volume's contents can then either be restored from a backup or reinitialized. stop Attempts to stop all volumes under the specified volume sets. The -f option can be used to forcibly stop a volume that is in use. This causes failures to be returned for any further I/O operations on the volume device. assoc Associates all volumes of the volume set, vset with the specified RVG, rvg. All the volumes of volume set must be of same usage type: either gen or fsgen. Volumes also cannot have an associated DRL. Note: If the RVG already has associated volumes, then the volumes of new volume set being associated should be of the same type as the existing volumes. All volumes in volume set being associated must be either VxVM ISP volumes or VxVM non-ISP volumes. dis Dissociates the named volume set, vset from its associated RVG. Dissociating the vset dissociates all the associated volumes of vset from the RVG. Note: The -f (force) option must be specified to force disassociation of the volume set from its associated RVG. OPTIONS
-c "ch_addopt" -c "ch_rmopt" Specifies a string that is passed to the vset_addvol content handler operation (if any) when a volume is added to a volume set, or that is passed to the vset_rmvol content handler operation (if any) when a volume is removed from a volume set. -f For the addvol and rmvol operations, forcibly adds or removes volumes to or from the volume set where this would otherwise not be allowed. For the start and stop operations, forcibly starts or stops volumes in the volume set where this would otherwise not be allowed. For the set operation, this option is required to forcibly set the makedev attribute to off or the compvol_access attribute to read-only if any of the component volumes of the volume set is open. -g diskgroup Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the vxdg(1M) manual page. -m "ch_initopt" Specifies a string that is passed to the vset_initset content handler operation (if any) when a volume set is initialized. -o compvol_access={read-only|read-write} If set to read-only, only reads are allowed on the raw device of each component volume of a volume set that is being cre- ated. If set to read-write, both reads and writes are allowed. This option only has any effect if the -o makedev=on option is also enabled for the volume set. If not specified, the default setting is read-only if -o makedev=on is speci- fied. -o index Specifies the index of a volume within a volume set. -o makedev={on|off} If set to on, sets up the raw device nodes for each of the component volumes in the volume set that is being created. If set to off (default), no raw device nodes are created. -t ch_subdir Specifies the subdirectory under /usr/lib/vxvm/content that contains the handler utilities for a volume set. For example, the VxFS handler utilities are located in the vxfs subdirectory. EXAMPLES
Create a volume set named acctvs containing the volume vol in the disk group mydg for use with VxFS: vxvset -g mydg -t vxfs make acctvs vol Similar to the previous example, but create raw device nodes for each component volume with read-write access to each node: vxvset -g mydg -t vxfs -o makedev=on -o compvol_access=read-write make acctvs1 vol1 Add the volumes, v1 and i-vol, to the volume set, acctvs, using specified index numbers: vxvset -g mydg -o index addvol acctvs v1 0 vxvset -g mydg -o index addvol acctvs i-vol 1 List the volumes in the volume set, acctvs: vxvset -g mydg list acctvs Remove the volume, v1, from the volume set, acctvs, by specifying its name: vxvset -g mydg rmvol acctvs v1 Remove the volume, i-vol, from the volume set, acctvs, by specifying its index number, 1: vxvset -g mydg -o index rmvol acctvs 1 Remove the raw device nodes from the volume set, acctvs1: vxvset -g mydg set makedev=off acctvs1 NOTES
Volume sets can be used in place of volumes with the following vxsnap operations on instant volume snapshots: addmir, dis, make, prepare, reattach, refresh, restore, rmmir, split, syncpause, syncresume, syncstart, syncstop, syncwait and unprepare. A full-sized snapshot of a volume set must itself be a volume set. See the vxsnap(1M) manual page for more information about administering instant volume snapshots. The maximum number of volumes that may be included in a volume set is 2048. Raw I/O is not supported for volume sets. Raw I/O from/to the component volumes of a volume set is if enabled by turning on the makedev attribute. This functionality is only sup- ported for private disk groups; it is not supported for shared disk groups in a cluster. If the makedev attribute is set to off, and you use the mknod command to create the raw device nodes, you cannot read from or write to those nodes unless you set the value of makedev to on. SEE ALSO
vxdg(1M), vxedit(1M), vxmake(1M), vxprint(1M), vxvol(1M) VxVM 5.0.31.1 24 Mar 2008 vxvset(1M)
All times are GMT -4. The time now is 07:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy