Sponsored Content
Full Discussion: rootvg mirrored
Operating Systems AIX rootvg mirrored Post 302645893 by newtoaixos on Thursday 24th of May 2012 08:56:52 AM
Old 05-24-2012
rootvg mirrored

I want to increase the size of /tmp by 1GB
I know that the command is
chfs -a size=+1G /tmp
But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks.
Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ?
Please advise.
 

10 More Discussions You Might Find Interesting

1. AIX

Mirrored disk.....

How do I know, which all disks are mirrored? any command? Bala (7 Replies)
Discussion started by: balaji_prk
7 Replies

2. AIX

Cloned Rootvg

New Question: The purpose of an alternate disk install is in my opinion to have a ready-to-use-backup and i've read that it is possible to install filesets or software on the cloned disk for testing purposal while the normal system is still running. The question is: how do you tell AIX (5.2... (5 Replies)
Discussion started by: kvanelshocht
5 Replies

3. AIX

mirror rootvg

Hello I have a question I have a box with Aix 5.3 with rootvg on mirror. I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one. My question is I can mirror this fs only ??? or I have to... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

4. AIX

Anyone know how to access rootvg?

I'm trying to troubleshoot an issue with an AIX system here. I have no experience with system administration of IBM stuff. Our local admin is ... um ... not available at this time. I found something online that said enter service mode - How the heck do I do that??? Why is IBM stuff lack proper... (2 Replies)
Discussion started by: bbbngowc
2 Replies

5. AIX

extendvg and rootvg

When attempting to extend rootvg to a new physical disk I received the following message: 0516-1162 extendvg: Warning, The Physical Partition Size of 64 requires the creation of 1093 partitions for hdisk5. The limitation for volume group rootvg is 1016 physical partitions... (4 Replies)
Discussion started by: jyoung
4 Replies

6. AIX

mirroring rootvg

I would like to konw wheather below steps are sufficient for mirroring rootvg. extendvg rootvg hdisk1 mirrorvg rootvg bootlist -m normal hdisk0 hdisk1 bosboot -ad hdisk0 bosboot -ad hdisk1 or anything needs to be added. (7 Replies)
Discussion started by: manoj.solaris
7 Replies

7. Solaris

Are my disks mirrored ?

# metastat d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 14582208 blocks (7.0 GB) d11: Submirror of d1 State: Okay Size: 14582208 blocks... (2 Replies)
Discussion started by: Exposure
2 Replies

8. AIX

How to extend mirrored VG?

Hi all, I need to extend a lv, but unfortunately I do not have enough space on my mirrored Volume group. I've planned to add 2 more disks to this vg (for mirroring) But ... what's the next steps to extend my lv using these 2 disks with a valid mirroring ? 1. extendvg myvg disk1 disk2... (3 Replies)
Discussion started by: unclefab
3 Replies

9. AIX

Need help in scripting to check if rootvg is mirrored or not

Hi Can some one help me with a script which when executed will check and tell if all the LV's in rootvg are mirrored or not. Say for example in the below server we could see that everything is mirrored except dumplv2. So if I execute the script it should tell that all are mirrored except... (7 Replies)
Discussion started by: newtoaixos
7 Replies

10. AIX

Reducing / on rootvg

The root filesystem was mirrored, someone/something stopped mirroring, and increased / and /home to ridiculous values (/ got increased to 102gb and its only using 4.3gb, so 98gb is free). Can I reduce the / (/dev/hd4) filesytem down WITHOUT corrupting the the OS? I would do a: chfs -a size=10g... (6 Replies)
Discussion started by: mrmurdock
6 Replies
vxtrace(1M)															       vxtrace(1M)

NAME
vxtrace - trace operations on volumes SYNOPSIS
vxtrace [-aeEls ] [-b buffersize] [-c eventcount] [-d outputfile] [-f inputfile] [-g diskgroup] [-k buffersize] [-m millisec_delay] [-o objtype [,objtype]...] [-t timeout] [-w waitinterval] [name | device]... DESCRIPTION
The vxtrace utility prints kernel error or I/O trace event records on the standard output or writes them to a file in binary format. Binary trace records written to a file can be read back and formatted by vxtrace as well. If no arguments are specified, vxtrace reports either all error trace data or all I/O trace data on all virtual disk devices. With error trace data, it is possible to select all accumulated error trace data, to wait for new error trace data, or both (the default). Selection can be limited to a specific disk group, to specific types of Veritas Volume Manager (VxVM) kernel I/O objects, or to particular named objects or devices. Under heavy loads, the kernel may discard one or more records before they can be reported to vxtrace. Even though the contents of the records are lost, the kernel keeps track of the number of lost records and reports this to vxtrace. as a record. vxtrace displays this record indicating that records were lost. You can increase the size of the kernel buffer using the -k buffersize option to reduce the likelihood of the kernel discarding records. OPTIONS
-a Appends to the outputfile instead of truncating it. By default, the output file is truncated. -b buffersize Sets the size of the buffer used by vxtrace when it obtains trace records from the kernel, or from a file when the -f option is specified. The buffer size is specified as a standard Veritas Volume Manager length (see vxintro(1M)). The default buffer size is 8K. -c eventcount Accumulates at most eventcount events and then exits. The timeout and eventcount options can be used together. -d outputfile Writes (dumps) binary trace data to the specified output file. -e Selects new error trace data. The default is to select I/O trace data. -E Selects pre-existing error trace data. This can be combined with -e to get both pre-existing trace data and new trace data. -f inputfile Reads binary trace data from the specified input file, instead of from the Veritas Volume Manager kernel. -g diskgroup Selects objects from the specified disk group. The disk group can be specified either by disk group ID or by disk group name. With no name or device arguments, all appropriate objects in the disk group are selected. With the name argument, diskgroup specifies the disk group that contains the named configuration record. -k buffersize Sets the kernel I/O trace buffer size. The Veritas Volume Manager kernel allocates a private kernel space to buffer the I/O trace records for each vxtrace command. The default buffer size is 8K bytes. Some trace records may be discarded if the trace buffer is too small. This option can be used to set a larger or a smaller kernel trace buffer size. The buffer size is speci- fied as a standard Veritas Volume Manager length (see vxintro(1M)). Depending on the Veritas Volume Manager kernel configura- tion, usually only a maximum buffer size of 1 megabyte is granted. -l Long format. Prints all available fields for all tracing records, instead of a subset of the available fields. The default is to use the short format. -m millisec_delay Pauses vxtrace for the specified period to allow more records to accumulate. name | device If name or device are specified, Veritas Volume Manager kernel objects of the requested types are selected if they are associated with the configuration records or virtual disk devices indicated by those arguments. -o objtype [,objtype]... Selects object based on the objtype option arguments. Multiple types of objects can be specified with one or several -o options. The possible object selection types are: all | ALL Selects all possible virtual disk devices, kernel objects, and physical disks. dev | logical Selects virtual disk devices. disk | physical Selects Veritas Volume Manager physical disks. log Selects all log objects. logplex Selects RAID-5 log plexes. logsd Selects DRL (dirty region logging) or RAID-5 log subdisks. logvol Selects DRL or RAID-5 log volumes. m | mv | mirror Selects mirrored volume kernel objects. p | pl | plex Selects striped or concatenated plex kernel objects. rl | rlink Selects RLINK kernel objects. If an RVG (replicated volume group) is specified, all RLINKs associated with that RVG are selected. s | sd | subdisk Selects subdisk kernel objects. v | vol | volume Selects mirrored or RAID-5 volume kernel objects. -s Specifies using synchronous writes to the outputfile instead of asynchronous writes. Asynchronous writes is the default. -t timeout Accumulates trace data for at most timeout seconds, then exits. -w waitinterval If vxtrace waits for waitinterval seconds without receiving any new events, prints waiting... to allow scripts to wake up and process previously accumulated events. This is useful for processing errors. The waiting... message does not count as an event for the purposes of the -c option. ARGUMENTS
Arguments specify configuration record names, or physical or virtual disk device nodes (by device path). If no object types were selected with the -o option, only trace records corresponding to the indicated configuration records or devices are selected; otherwise, objects of the requested types are selected if they are associated in any way with the named configuration record or device. If a name argument does not match a regular configuration record, but does match a disk access record, the indicated physical disk is selected. Physical disks can also be selected by the disk media record name. By default, name arguments are searched for in the default disk group (defaultdg) unless a disk group is specified using the -g option. The disk group for any individual name argument can be overridden using the form: diskgroup/recordname Note: When reading trace data from a file with the -f option, association information is not available. EXAMPLES
To trace all physical disk I/Os, enter: vxtrace -o disk To trace virtual disk device I/Os to the device associated with volume testvol, use either of the commands: vxtrace -g testdg -o dev testvol vxtrace /dev/vx/dsk/testdg/testvol To trace all log subdisks associated with volume testvol, enter: vxtrace -g testdg -o logsd testvol To trace all log objects, enter: vxtrace -o log To accumulate ten seconds worth of trace data for disk04 and then format that data, use: vxtrace -t 10 -d /tmp/tracedata disk04 vxtrace -l -f /tmp/tracedata To read error trace data into a script for processing, using ten second pauses to generate mail messages, use the command: vxtrace -leE -w 10 | while read ... FILES
/dev/vx/trace SEE ALSO
vxintro(1M), vxstat(1M), vxtrace(7) VxVM 5.0.31.1 24 Mar 2008 vxtrace(1M)
All times are GMT -4. The time now is 09:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy