Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Regarding AIX volume manager & replacing a disk
Operating Systems AIX Regarding AIX volume manager & replacing a disk Post 302622563 by zaxxon on Thursday 12th of April 2012 10:33:29 AM
Old 04-12-2012
mirrorvg will follow the settings for the LVs to be mirrored. So if they are set to "strict", at least every PP of the mirrored LP will be placed on a different PV in a VG. If you have more than 2 PVs in a VG they can be scattered on PVs you did not intend to use. Ie. it could happen that if disks on one side get broken, it could hit both mirror copies of the LP which is what should be avoided at all costs and what you are trying to do.

Code:
# lslv root_lv| grep EACH
EACH LP COPY ON A SEPARATE PV ?: yes

But to make sure there is no mixup of PPs belonging to different mirrored LVs from the same VG, you can check this placement with for example:
Code:
# lsvg -M rootvg

You see things like:
Code:
hdisk1:280      hd4:6:2

From the man page of lsvg, specifically -M:
Code:
PVname:PPnum [LVname: LPnum [:Copynum] [PPstate]]

(PPstate is not displayed here)
So if you see the same LV name with :1 and :2, which is the copy number on the same PV (hdisk1), then you have a problem - it would mean the allocation of LP copies is not strict for that LV. If you have LP copies of one LV on the same PV as that from another mirrored LV, then you have a problem too, as from your description you want to have both LV copies on separate disks, ie. each LV mirror has his dedicated mirror disk/PV.
To rearrange the placement you will have to use the command migratelp to move the LPs to the correct PV (note that the order of arguments/parameters of migratelp is different to the order you get from the output of lsvg -M!).
That's a lot of work so a script scanning for wrong placement and then migrating to free PPs is a bit of work, but helpful.

By this you can also check if the placement is/was as wanted, before you changed the disk.
Last edited by zaxxon; 04-12-2012 at 11:59 AM.. Reason: rearranged and added info, spelling etc.
 

10 More Discussions You Might Find Interesting

1. Solaris

Disk Mirror in Solaris 9 via Solaris Volume Manager

Hello, I am trying to do mirror in solaris 9. I have total 0-7 disks 4 5 6 7 0 1 2 3 Drive 0 and Drive 4 = Boot Drives Need to Mirror following drives. Drive 1 and Drive 5 = Need to mirror Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5. Then i... (3 Replies)
Discussion started by: deal732
3 Replies

2. Filesystems, Disks and Memory

Volume Manager; importing a disk

System: Alpha with Tru64 5.1b Disk under LSM (Logical Storage Manager; essentially v2 of Veritas VxVM) control was generating disk errors. The disk was timing out a lot and generating a few disk errors. DBAs couldn't keep the oracle instance up on that node of the cluster. I contacted HP and got... (1 Reply)
Discussion started by: BOFH
1 Replies

3. Solaris

Need some E-Labs for solaris 10 & veritas volume manager

Hello friends, I need to test some of the solaris 10 concepts and veritas volume manager.i want to know ,where i get the testing labs or E-labs(online) for this practice.i ready to pay for this labs.pls kindly help me to get the details or website names...Thanks in Advance -Jay (6 Replies)
Discussion started by: rjay.com
6 Replies

4. UNIX for Advanced & Expert Users

Veritas Volume Manager question (Disk layout with 4 plexes)

I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is: usbtor12# vxprint -hrtg appdg v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 Replies)
Discussion started by: momin313
3 Replies

5. Solaris

Veritas Volume Manager: disk "failed was"

Hello there, I'm going to describe a situation I've got here... feel free to ask away questions and I'll provide what I can if it'll help me get this answered! When I do a vxdisk list, I see a disk that VxVM calls "disk4" that is listed as "failed was: c1t9d0s2". When I do a format, I can go... (3 Replies)
Discussion started by: kitykity
3 Replies

6. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

7. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% / ... (0 Replies)
Discussion started by: fretagi
0 Replies

9. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies

LEARN ABOUT HPUX

vxbrk_rootmir

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 06:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy