Sponsored Content
Full Discussion: VxVM confused by SDS?
Operating Systems Solaris VxVM confused by SDS? Post 302438538 by Beast Of Bodmin on Tuesday 20th of July 2010 04:35:16 AM
Old 07-20-2010
Question VxVM confused by SDS?

I have an old V490 running an old version of Soalris 10 and an old version of VxVM.

The system disks are configured using metathis and metathat, the remaining disks

Because of the brain-damaged way engineering run things here, I cannot change this. I cannot upgrade nor patch the OS. I cannot upgrade nor patch VxVM.

I recently successfully replaced the root disk, and rebuilt the root mirror. But consequently vxdisk list complains about the replaced device.

Code:
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto            -            -            error
c0t1d0s2     auto:none       -            -            online invalid

How can I get c0t0d0s2 to transition to "online invalid"?

Code:
# uname -a
SunOS zus15d-4403 5.10 Generic_127111-02 sun4u sparc SUNW,Sun-Fire-V490

# pkginfo -l VRTSvxvm
   PKGINST:  VRTSvxvm
      NAME:  VERITAS Volume Manager, Binaries
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  4.1,REV=02.17.2005.21.28
   BASEDIR:  /
    VENDOR:  VERITAS Software
      DESC:  Virtual Disk Subsystem
    PSTAMP:  VERITAS-4.1_MP2_RP2_HF1:2007-09-29
  INSTDATE:  Feb 26 2008 19:21
   HOTLINE:  800-342-0652
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      847 installed pathnames
                  17 partially installed pathnames
                  35 shared pathnames
                  18 linked files
                  98 directories
                 429 executables
              301445 blocks used (approx)


Last edited by Scott; 07-20-2010 at 10:48 AM.. Reason: Code tags, please...
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

New Sds Slice

Hi, I'd like to add two new disk (mirrored each other) in a machine still on line. The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk. who could send me exemples or tell me how to... (1 Reply)
Discussion started by: guillaume35
1 Replies

2. UNIX for Advanced & Expert Users

SDS and replicas

Hello, We are using Solstice Disk Suite on Solaris 2.7. We want to add two striped volume with six disks. On each disk, we take a slice and we create the stripe. That I want to know : Is it necessary to add two replicas on the same slice on the new disks, as made before on the others... (1 Reply)
Discussion started by: christophe
1 Replies

3. UNIX for Advanced & Expert Users

SDS to Veritas migration

...I have a situation where I disks that I mirrored using Solstice Disksuite now need mirroring under Veritas Volume manager...would anyone know the best way to go about 'un-mirroring' and then removing SDS? I can see references in /etc/vfstab and /etc/system that I guess would need... (2 Replies)
Discussion started by: silvaman
2 Replies

4. 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

5. Solaris

VxVM softpartitions

Is there a way to create "softpartitions" with Veritas Volume Manager? I have a bunch of disks and i want to create a RAID 5 with them. On that RAID5, i want to split that RAID into two separated file systems like i could do it with SDS/LVM or ZFS, but i don't want to create two RAID5 in the... (3 Replies)
Discussion started by: pressy
3 Replies

6. Solaris

VxVM..anything to worry about in here..

DEVICE TYPE DISK GROUP STATUS c0t0d0s2 sliced rootdisk rootdg online c1t1d0s2 sliced disk01 rootdg online c2t0d0s2 sliced actsvr101 actsvr1dg online c2t2d0s2 sliced actsvr102 actsvr1dg online c2t3d0s2 ... (13 Replies)
Discussion started by: incredible
13 Replies

7. Solaris

VxVM on Solaris.

Hi, Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies

8. Solaris

T6340/SDS root disk pull test.

Here's the scenario.. Server built with solaris 10 + SDS to mirror OS disk to 2nd disk. If you pull the root disk while the system is running, would you expect : 1, The box to just stay running, ie off its mirror 2, The box would crash, reboot, try and boot of its primary, if not, the... (4 Replies)
Discussion started by: itsupplies
4 Replies

9. 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

10. AIX

IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ?

I'd like to add some x/linux-based servers to my current AIX-based TDS/SDS server community. Reading the Fine Install Guide (rtfig ?) I believe this may be covered by the section "Upgrade an instance of a previous version to a different computer" i.e. I'm going to install latest/greatest SDS on a... (4 Replies)
Discussion started by: maraixadm
4 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 08:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy