Sponsored Content
Full Discussion: Display Mirror State AIX
Top Forums UNIX for Dummies Questions & Answers Display Mirror State AIX Post 38166 by RTM on Tuesday 8th of July 2003 11:09:20 AM
Old 07-08-2003
Removing the -m option will bring you back to default which lists 20+ different variables.

Code:
If no flags are specified, the following status is displayed:

Logical volume Name of the logical volume. Logical volume names must be unique systemwide and can range from 1 to 15 characters. 
Volume group Name of the volume group. Volume group names must be unique systemwide and can range from 1 to 15 characters. 
Logical volume identifier Identifier of the logical volume. 
Permission Access permission; read-only or read-write. 
Volume group state State of the volume group. If the volume group is activated with the varyonvg command, the state is either active/complete (indicating all physical volumes are active) or active/partial (indicating all physical volumes are not active). If the volume group is not activated with the varyonvg command, the state is inactive. 
Logical volume state State of the logical volume. The Opened/stale status indicates the logical volume is open but contains physical partitions that are not current. Opened/syncd indicates the logical volume is open and synchronized. Closed indicates the logical volume has not been opened. 
Type Logical volume type. 
Write verify Write verify state of On or Off. 
Mirror write consistency Mirror write consistency state of Yes or No. 
Max LPs Maximum number of logical partitions the logical volume can hold. 
PP size Size of each physical partition. 
Copies Number of physical partitions created for each logical partition when allocating. 
Schedule policy Sequential or parallel scheduling policy. 
LPs Number of logical partitions currently in the logical volume. 
PPs Number of physical partitions currently in the logical volume. 
Stale partitions Number of physical partitions in the logical volume that are not current. 
Bad blocks Bad block relocation policy. 
Inter-policy Inter-physical allocation policy. 
Strictness Current state of allocation, strict, nonstrict, or superstrict. A strict allocation states that no copies for a logical partition are allocated on the same physical volume. If the allocation does not follow the strict criteria, is is called nonstrict. A nonstrict allocation states that at least one occurrence of two physical partitions belong to the same logical partition. A superstrict allocation states that no partition from one mirror copy may reside the same disk as another mirror copy. 
Intra-policy Intra-physical allocation policy. 
Upper bound If the logical volume is super strict, upper bound is the maximum number of disks in a mirror copy. 
Relocatable Indicates whether the partitions can be relocated if a reorganization of partition allocation takes place. 
Mount point File system mount point for the logical volume, if applicable. 
Label Specifies the label field for the logical volume. 
PV distribution The distribution of the logical volume within the volume group. The physical volumes used, the number of logical partitions on each physical volume, and the number of physical partitions on each physical volume are shown. 
striping width The number of physical volumes being striped across. 
strip size The number of bytes per stripe.

 

10 More Discussions You Might Find Interesting

1. Solaris

ZFS Mirror versus Hardware Mirror

I've looked a little but haven't found a solid answer, assuming there is one. What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies

2. AIX

AIX Rootvg mirror and sysdumplv

Guys, In my AIX 6.1 box the rootvg was on hdisk2, I tried to migrated it to hdisk0 Added hisk0 to rootvg , mirrored rootvg and changed bootlist and and sucessfully rebooted from hdisk0 Now I tried to remove the hdisk2 from rootvg so breaked mirror -bash-3.00# unmirrorvg rootvg hdisk2... (3 Replies)
Discussion started by: kkeng808
3 Replies

3. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

4. HP-UX

What is the difference between DRD and Root Mirror Disk using LVM mirror ?

what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies

5. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

6. AIX

AIX break rootvg mirror from system down

Hello, aix 5.2, mirrored rootvg on hdisk0 and hdisk1. hdisk0 is dead. I can boot to cd, into sms, into maintenance mode. I can fsck all the various partitions on hdisk1 (the hd4 hd2 hd3, etc...) all is fine. But without the hdisk0 part of the mirror I cannot get the system to boot. ystem hangs on... (6 Replies)
Discussion started by: sshapiro
6 Replies

7. AIX

How to manually -re-attach AIX lv's to a mirror?

in trying to rectify a stale lv problem I ran rmlvcopy <lv> 1 <primary disk> leaving the original os disk without lv copies other than the stale lv. Both disks seem operational, but, lsvg rootg shows 1 stale pv. The end goal is to re-attach the lv's back to hdisk1, and then attempt a reboot... (11 Replies)
Discussion started by: mrmurdock
11 Replies

8. AIX

AIX hdisk Mirror vs alt_clone

Hello, I have two hdisk in Power7 machine, the rootvg on hdisk0. So to make a disk redundancy should make mirror or alt_clone and what is the different. Appreciate your help Thanks (1 Reply)
Discussion started by: moudmm
1 Replies

9. UNIX for Beginners Questions & Answers

AIX - mirror a jfs2log

Hi everybody, I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirroring. I accidentally created logical volume cpsabcd2lv with external jfs2log loglv00 in the same volume group cpsdata2vg. Then I mirrored LV cpsabcd2lv on the second LUN in VG cpsdata2vg. My journal is unmirrored and... (0 Replies)
Discussion started by: Necronomic
0 Replies

10. AIX

AIX lsvg strange LV STATE and MOUNT POINT

What does it mean when your LV STATE changes to closed/syncd? What does it mean when your mount point is #? I was not able to mount it or write data to it. So in this case since there was no data in /opt/cvt I used rmlv to get rid of it. Why did I have to manually edit /etc/filesystems to get rid... (1 Reply)
Discussion started by: cokedude
1 Replies
metastat(1M)						  System Administration Commands					      metastat(1M)

NAME
metastat - display status for metadevice or hot spare pool SYNOPSIS
/usr/sbin/metastat -h /usr/sbin/metastat [-a] [-B] [-D] [-c] [-i] [-p] [-q] [-s setname] [-t] [metadevice...] [hot_spare_pool...] /usr/sbin/metastat [-a] [-B] [-D] [-c] [-i] [-p] [-q] [-s setname] component... DESCRIPTION
The metastat command displays the current status for each metadevice (including stripes, concatenations, concatenations of stripes, mir- rors, RAID5, soft partitions, and trans devices) or hot spare pool, or of specified metadevices, components, or hot spare pools. It is helpful to run the metastat command after using the metattach command to view the status of the metadevice. metastat displays the state of each Solaris Volume Manager RAID-1 volume on the system. The possible states include: Okay The device reports no errors. Needs maintenance A problem has been detected. This requires that the system administrator replace the failed physical device. Volumes displaying Needs maintenance have incurred no data loss, although additional failures could risk data loss. Take action as quickly as possible. Last erred A problem has been detected. Data loss is a possibility. This might occur if a component of a submirror fails and is not replaced by a hot spare, therefore going into Needs maintenance state. If the corresponding component also fails, it would go into Last erred state and, as there is no remaining valid data source, data loss could be a possibility. Unavailable A device cannot be accessed, but has not incurred errors. This might occur if a physical device has been removed with Solaris Dynamic Reconfiguration (DR) features, thus leaving the Solaris Volume Manager volume unavailable. It could also occur if an array or disk is powered off at system initialization, or if a >1TB volume is present when the system is booted in 32-bit mode. After the storage has been made available, run the metastat command with the -i option to update the status of the metadevices. This clears the unavailable state for accessible devices. See the for instructions on replacing disks and handling volumes in Needs maintenance or Last erred states. OPTIONS
The following options are supported: -a Display all disk sets. Only metadevices in disk sets that are owned by the current host are displayed. -B Display the current status of all of the 64-bit metadevices and hot spares. -c Display concise output. There is one line of output for each metadevice. The output shows the basic structure and the error status, if any, for each metadevice. The -c output format is distinct from the -p output format. The -p option does not display metadevice status and is not intended as human-readable output. -D Display the current status of all of the descriptive name metadevices and hotspares. -h Display usage message. -i Check the status of RAID-1 (mirror) volumes, RAID-5 volumes, and hot spares. The inquiry checks each metadevice for accessi- bility, starting at the top level metadevice. When problems are discovered, the metadevice state databases are updated as if an error had occurred. -p Display the list of active metadevices and hot spare pools in the same format as md.tab. See md.tab(4). The -p output is designed for snapshotting the configuration for later recovery or setup. -q Display the status for metadevices without the device relocation information. -s setname Specify the name of the disk set on which metastat works. Using the -s option causes the command to perform its administra- tive function within the specified disk set. Without this option, the command performs its function on metadevices and hot spare pools in the local disk set. -t Display the current status and timestamp for the specified metadevices and hot spare pools. The timestamp provides the date and time of the last state change. OPERANDS
The following operands are supported: component Display the status of the component hosting a soft partition, including extents, starting blocks, and block count. hot_spare_pool Display the status of the specified hot spare pool(s). metadevice Display the status of the specified metadevice(s). If a trans metadevice is specified, the status of the master and log devices is also displayed. Trans metadevices have been replaced by UFS logging. See NOTES. EXAMPLES
Example 1 Output Showing Mirror with Two Submirrors The following example shows the partial output of the metastat command after creating a mirror, opt_mirror, consisting of two submirrors, opt_sub1 and opt_sub2. # metastat opt_mirror opt_mirror: Mirror Submirror 0: opt_sub1 State: Okay Submirror 1: opt_sub2 State: Resyncing Resync in progress: 15 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 2006130 blocks . . . Example 2 Soft Partition on Mirror with Submirror The following example shows the partial output of the metastat command after creating a soft partition, d3, on concat d2, which is built on a soft partition. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 3 Trans Metadevice The following example shows the output of the metastat command after creating a trans metadevice. # metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752 Example 4 Multi-owner disk set The following example shows the output of the metastat command with a multi-owner disk set and application-based mirror resynchronization option. Application-based resynchronization is set automatically if needed. # metastat -s oban oban/d100: Mirror Submirror 0: oban/d10 State: Okay Submirror 1: oban/d11 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Resync option: application based Owner: None Size: 1027216 blocks (501 MB) oban/d10: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t3d0s0 0 No Okay oban/d11: Submirror of oban/d100 State: Okay Size: 1027216 blocks (501 MB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t4d0s0 0 No Okay WARNINGS
metastat displays states as of the time the command is entered. It is unwise to use the output of the metastat -p command to create a md.tab(4) file for a number of reasons: o The output of metastat -p might show hot spares being used. o It might show mirrors with multiple submirrors. See metainit(1M) for instructions for creating multi-way mirrors using metainit and metattach. o A slice may go into an error state after metastat -p is issued. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdr | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) NOTES
Trans metadevices have been replaced by UFS logging. Existing trans devices are not logging--they pass data directly through to the under- lying device. See mount_ufs(1M) for more information about UFS logging. SunOS 5.11 26 Mar 2006 metastat(1M)
All times are GMT -4. The time now is 07:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy