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
PERLOS400(1)						 Perl Programmers Reference Guide					      PERLOS400(1)

NAME
README.os400 - Perl version 5 on OS/400 DESCRIPTION
This document describes various features of IBM's OS/400 operating system that will affect how Perl version 5 (hereafter just Perl) is compiled and/or runs. By far the easiest way to build Perl for OS/400 is to use the PASE (Portable Application Solutions Environment), for more information see http://www.iseries.ibm.com/developer/factory/pase/index.html This environment allows one to use AIX APIs while programming, and it provides a runtime that allows AIX binaries to execute directly on the PowerPC iSeries. Compiling Perl for OS/400 PASE The recommended way to build Perl for the OS/400 PASE is to build the Perl 5 source code (release 5.8.1 or later) under AIX. The trick is to give a special parameter to the Configure shell script when running it on AIX: sh Configure -DPASE ... The default installation directory of Perl under PASE is /QOpenSys/perl. This can be modified if needed with Configure parameter -Dprefix=/some/dir. Starting from OS/400 V5R2 the IBM Visual Age compiler is supported on OS/400 PASE, so it is possible to build Perl natively on OS/400. The easier way, however, is to compile in AIX, as just described. If you don't want to install the compiled Perl in AIX into /QOpenSys (for packaging it before copying it to PASE), you can use a Configure parameter: -Dinstallprefix=/tmp/QOpenSys/perl. This will cause the "make install" to install everything into that directory, while the installed files still think they are (will be) in /QOpenSys/perl. If building natively on PASE, please do the build under the /QOpenSys directory, since Perl is happier when built on a case sensitive filesystem. Installing Perl in OS/400 PASE If you are compiling on AIX, simply do a "make install" on the AIX box. Once the install finishes, tar up the /QOpenSys/perl directory. Transfer the tarball to the OS/400 using FTP with the following commands: > binary > site namefmt 1 > put perl.tar /QOpenSys Once you have it on, simply bring up a PASE shell and extract the tarball. If you are compiling in PASE, then "make install" is the only thing you will need to do. The default path for perl binary is /QOpenSys/perl/bin/perl. You'll want to symlink /QOpenSys/usr/bin/perl to this file so you don't have to modify your path. Using Perl in OS/400 PASE Perl in PASE may be used in the same manner as you would use Perl on AIX. Scripts starting with #!/usr/bin/perl should work if you have /QOpenSys/usr/bin/perl symlinked to your perl binary. This will not work if you've done a setuid/setgid or have environment variable PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the latest PTFs to have this feature. Scripts starting with #!/QOpenSys/perl/bin/perl should always work. Known Problems When compiling in PASE, there is no "oslevel" command. Therefore, you may want to create a script called "oslevel" that echoes the level of AIX that your version of PASE runtime supports. If you're unsure, consult your documentation or use "4.3.3.0". If you have test cases that fail, check for the existence of spool files. The test case may be trying to use a syscall that is not implemented in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL environment variable or have a handler for the SIGILL. If you can compile programs for PASE, run the config script and edit config.sh when it gives you the option. If you want to remove fchdir(), which isn't implement in V5R1, simply change the line that says: d_fchdir='define' to d_fchdir='undef' and then compile Perl. The places where fchdir() is used have alternatives for systems that do not have fchdir() available. Perl on ILE There exists a port of Perl to the ILE environment. This port, however, is based quite an old release of Perl, Perl 5.00502 (August 1998). (As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 has been out since April 2001.) If you need to run Perl on ILE, though, you may need this older port: http://www.cpan.org/ports/#os400 Note that any Perl release later than 5.00502 has not been ported to ILE. If you need to use Perl in the ILE environment, you may want to consider using Qp2RunPase() to call the PASE version of Perl. AUTHORS
Jarkko Hietaniemi <jhi@iki.fi> Bryan Logan <bryanlog@us.ibm.com> David Larson <larson1@us.ibm.com> perl v5.12.1 2010-04-26 PERLOS400(1)
All times are GMT -4. The time now is 05:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy