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
voltrace(8)						      System Manager's Manual						       voltrace(8)

NAME
voltrace - Trace operations on volumes SYNOPSIS
/usr/sbin/voltrace [-eEla] [-d outputfile] [-f inputfile] [-t timeout] [-c eventcount] [-w waitinterval] [-b buffersize] [-g diskgroup] [-o objtype[,objtype]...] [name | device]... OPTIONS
The following options are recognized by voltrace: Selects new error trace data. The default is to select I/O trace data. Selects pre- existing error trace data. This can be combined with -e to get both preexisting trace data and new trace data. Specifies long format. Prints all available fields for all tracing records, rather than a subset of the available fields. The default is to use the short format. Writes (dumps) binary trace data to the specified output file. Appends to the outputfile rather than truncating it. By default, the out- put file is truncated. Reads binary trace data from the specified input file, rather than from the kernel. Accumulates trace data for at most timeout seconds and then exits. Accumulates at most eventcount events and then exits. The timeout and eventcount options can be used together. If voltrace waits for waitinterval seconds without receiving any new events, prints the message waiting... to allow scripts to wake up and process previously accumulated events. This is mostly of use for processing errors. The waiting... message does not count as an event for the purposes of the -c option. Sets the kernel I/O trace buffer size or sets the read buffer size when used with the -f option. The Logical Storage Manager kernel allocates a private kernel space to buffer the I/O trace records for each voltrace 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 specified as a standard Logical Storage Manager length (see volintro(8)). Depending on the Logical Storage Manager kernel configuration, usually only a maximum of 64K bytes buffer size will be granted. 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 operands, all appropriate objects in the disk group are selected. With name operands, diskgroup names the disk group that is expected to contain the named configuration record. 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: Selects mirrored or RAID-5 volume kernel objects. Selects striped or concatenated plex kernel objects. Selects mirrored volume kernel objects. Selects subdisk kernel objects. Selects LSM physical disks. Selects virtual disk devices. Selects DRL or RAID-5 log volumes. Selects RAID-5 log plexes. Selects DRL or RAID-5 log subdisks. Selects all log objects. Selects all possible virtual disk devices, kernel objects and physical disks. If name or device operands are provided, kernel objects of the requested types are selected if they are associated with the configuration records or virtual disk devices indicated by those operands. DESCRIPTION
The voltrace 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 voltrace as well. If no operands are given, either all error trace data or all I/O trace data on all virtual disk devices are reported. 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 kernel I/O object types, or to particular named objects or devices. OPERANDS
Operands 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 device path of the public region partition, or by the disk media record name. By default name arguments are searched for in all disk groups or in the disk group specified using the -g option. Without the -g option, a record that is found in more than one disk group will cause an error unless the record is in the rootdg disk group (in which case, the record in the rootdg disk group is selected). The disk group for any individual name operand 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, use the command: # voltrace -o disk To trace virtual disk device I/Os to the device associated with volume testvol, use either of the commands: # voltrace -o dev testvol # voltrace /dev/vol/testvol To trace all log subdisks associated with volume testvol, use the command: # voltrace -o logsd testvol To trace all log objects, use the command: # voltrace -o log To accumulate 10 seconds worth of trace data for disk04 and then format that data, use the command: # voltrace -t 10 -d /tmp/tracedata disk04 # voltrace -l -f /tmp/tracedata To read error trace data into a script for processing, using 10 second pauses to generate mail messages, use the command: # voltrace -leE -w 10 | while read... FILES
Default device to which events are logged. SEE ALSO
volintro(8), volnotify(8), volstat(8) voltrace(8)
All times are GMT -4. The time now is 08:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy