Sponsored Content
Operating Systems AIX logical volume partially mirrored Post 302206382 by shockneck on Tuesday 17th of June 2008 02:36:41 PM
Old 06-17-2008
Quote:
Originally Posted by lo-lp-kl
[...] if I type lsvg -l rootvg I got this

0516-1147 : Warning - logical volume waslv may be partially mirrored.
waslv jfs2 277 477 3 open/syncd /usr/WebSphere

If I type lslv -m waslv |more

waslv:/usr/WebSphere
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0299 hdisk0 0305 hdisk1
0002 0300 hdisk0 0306 hdisk1
0003 0301 hdisk0 0307 hdisk1
0004 0302 hdisk0 0308 hdisk1
0005 0303 hdisk0 0309 hdisk1
0006 0304 hdisk0 0310 hdisk1
0007 0305 hdisk0 0311 hdisk1
0008 0306 hdisk0 0312 hdisk1
.................... .............


My question is If I type the command syncvg -v rootvg I can fix my problem ?? [...]
The first output implies that you used three disks for your mirror. The second output seem to imply that one complete disk got missing. So you might have two mirror copies spread uneven over three disks of which you lost one. Use
# lsvg -p <yourvg>
to find out whether a PV went missing.
If that was the case a syncvg will not help as your mirror was not stale but broken. Backup your data and then repair the mirror(s). If you decide to unmirror the lv/vg let LVM sort out which copy to keep!
 

10 More Discussions You Might Find Interesting

1. AIX

checking to see if logical disks are mirrored.

I have AIX 5.1 I ran these commands and was not able to see what disk were mirrored to what. I thought this is what I should do? lslv -m rd |more lslv -m db |more I get a error stating that it can't find or in the device configuation databse. Is there another way to look? I have a physcal... (1 Reply)
Discussion started by: rocker40
1 Replies

2. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

3. AIX

Moving a Logical Volume from one Volume Group to Another

Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies

4. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

5. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. HP-UX

[Solved] How to extend a mirrored logical volume?

Want to extend the /home filesystem: Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol4 262144 260088 2056 99% /home root@server:./root # vgdisplay vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 11 Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies

8. AIX

Position of the logical volume on the physical volume

Hello everyone, I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created. When I say region I mean: outer edge - outer middle - center - inner middle and inner edge. Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies

9. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME
vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation SYNOPSIS
/etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b] [-t tasktag] {daname|dmname} DESCRIPTION
The vxbrk_rootmir command creates a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the broken-off mirror into a completely separate root disk that is suitable for booting by itself. Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks. A valid root mirror disk should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained. The given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror. If so, the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk. If the specified disk is not a valid root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur- rent VxVM root disk. After the mirroring operation is complete, the mirror is then broken off, and regenerated into a unique VxVM root disk. OPTIONS
-b Uses the setboot command to set the alternate boot disk to the specified disk. If the -v option is also specified, information is displayed about the current setboot settings. -g diskgroup Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created if it does not already exist. If the disk group already exists, the broken-off mirror is added to it. If this option is not specified, the disk group of the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk group to prevent the mirror from being automatically imported. -t tasktag Marks any tasks that are registered to track the progress of an operation with the specified tag, tasktag. This option is passed to vxrootmir if it is necessary first to mirror the specified disk that is to be broken off. -v Displays verbose output, including timestamps for operations that are in progress. This option is passed to vxrootmir if it is neces- sary first to mirror the specified disk that is to be broken off. ARGUMENTS
daname Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as the broken off mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0 VxVM vxbrk_rootmir INFO V-5-2-4023 17:47: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4025 17:47: DA c4t15d0s2, DM rootdisk06 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4052 17:47: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 17:47: Breaking off root mirror on DA c4t15d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 17:47: Setting broken off mirror on c4t15d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 17:47: Preparing disk c4t15d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 17:47: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 17:47: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 17:48: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 17:48: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 17:48: Alternate: 0/2/1/0.8.0.255.2.5.0 VxVM vxbrk_rootmir INFO V-5-2-4042 17:48: Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 17:48: Disk c4t15d0s2 is now a broken off root disk The next example shows the command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be called to mirror the root disk first: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0 VxVM vxbrk_rootmir INFO V-5-2-4023 16:25: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk VxVM vxrootmir INFO V-5-2-2501 16:25: Gathering information on the current VxVM root configuration VxVM vxrootmir INFO V-5-2-2441 16:25: Checking specified disk(s) for usability VxVM vxrootmir INFO V-5-2-2566 16:25: Preparing disk c5t5d0 as a VxVM root disk VxVM vxrootmir INFO V-5-2-3766 16:25: Disk c5t5d0 is now EFI partitioned disk c5t5d0s2 VxVM vxrootmir INFO V-5-2-2410 16:25: Adding disk c5t5d0s2 to brkdg as DM rootdisk03 VxVM vxrootmir INFO V-5-2-1646 16:25: Mirroring all volumes on root disk VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol VxVM vxrootmir INFO V-5-2-1616 16:40: Disk c5t5d0s2 is now a mirrored root disk VxVM vxbrk_rootmir INFO V-5-2-4052 16:40: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 16:40: Breaking off root mirror on DA c5t5d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 16:40: Setting broken off mirror on c5t5d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 16:40: Preparing disk c5t5d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 16:41: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 16:41: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 16:41: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 16:41: Alternate: 0/2/1/0.8.0.255.2.0.0 VxVM vxbrk_rootmir INFO V-5-2-4042 16:41: Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 16:41: Disk c5t5d0s2 is now a broken off root disk SEE ALSO
vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 03:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy