Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: VxVM not able to see new disk
Homework and Emergencies Emergency UNIX and Linux Support VxVM not able to see new disk Post 302760279 by NielGreeff on Wednesday 23rd of January 2013 06:02:24 PM
Old 01-23-2013
Solaris_1977

Let me explain new LUNS and the discovery from the VxVM side ....

When the OS discovers a new LUN, there is a new daemon , called ESD (Event Source Daemon) that tries to do the "windows" "plug&play" bit.

Once a new LUN is discovered , ESD then broadcasts to all registered software (like EMCP and VxVM) that there is a new LUN.

Now, here comes the problem.

VxVM and EMCP sees the new LUN at the same time.
EMCP starts creating a new powerdevice for it, and VxVM creates a new disk record for it.

When EMC powerpath created the device, it again sends a message to ESD and ESD then broadcasts this to the other registered software (VxVM).

VxVM now tries to "link" the power device with the disk ...
The reason is that PowerPath already does DMP, and if VxVM also does DMP, you get double the work and double the time for IO.... VxVM does NOT do DMP to powerdevices to eliminate this double work. So, VxVM has to make the "link" between the disk and the power device .....

Now comes the problem.

This all happens so fast, because in the process, VxVM also sends out a ESD broadcast saying that it knows about a new disk and it can do DMP for it (which EMCP picks up and checks and .....)

OK, so how can you solve this ?

The best way is to stop VxVM from "linking" into ESD.
There is a process called "vxesd" (do a "ps" to see)

If you call support, they will tell you to stop VxVM ESD by looking at this link ....
(explains what I did above in more detail and gives the commands to stop it running)


(oops, can not yet post links ... so go to google and search for symanetc and TECH72540)




When the machine rebooted, the device discovery was done by the OS, then PowerPath and then VxVM (correct order), and as such eliminated the problems.

The steps that you followed (scandisks ...) is 100% correct, and should be followed once you have stopped vxesd from running again.

If you do have further questions, please feel free to ask, or if you want me to look at data on your specific machine, let me know
 

10 More Discussions You Might Find Interesting

1. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies

2. UNIX for Advanced & Expert Users

VxVM disk/lun grow

hi, i have a volume on a LUN of an EMC-storage and i need to increase the size. i could increase the size of the LUN on the EMC, i could increase the size of the disk for solaris, but how can i tell the veritas volume manager that the disk is larger now? what i've done: 1. LUN on EMC 2.... (3 Replies)
Discussion started by: pressy
3 Replies

3. Solaris

How to add disk into Striped Volume VxVM

VxVM: How to add one more disk into v08 the stripe should change from 7/128 to 8/128 v v08 - ENABLED ACTIVE 8954292224 SELECT v08-01 fsgen pl v08-01 v08 ENABLED ACTIVE 8954292480 STRIPE 7/128 RW sd bkpdg35-01 v08-01 bkpdg35 17216 ... (0 Replies)
Discussion started by: geoffry
0 Replies

4. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

5. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

6. Solaris

vxvm root disk booting problem - solved with boot -a. How?

Hi All, We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear: WARNING: Error writing ufs log state WARNING: ufs log for / changed state to Error WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies

7. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies

8. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

9. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

10. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 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 08:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy