Sponsored Content
Full Discussion: SVM question
Operating Systems Solaris SVM question Post 302355757 by NewSolarisAdmin on Wednesday 23rd of September 2009 03:43:01 PM
Old 09-23-2009
Quote:
Originally Posted by seg
The man page for metainit has examples for concatenation. Additionally Sun's documentation of SVM has explicit examples for setting up a RAID 10 or 0+1.
Setting up s0 or s1 as the data slice then using s7 for metadb is a good idea and you should stick with that.

Chapter 9 RAID-0 (Stripe and Concatenation) Volumes (Tasks)
Chapter 11 RAID-1 (Mirror) Volumes (Tasks)
Thanks for the links. Lots of good info in there. I understand all of the pieces, it's just how to put them together that I am having trouble with...
 

10 More Discussions You Might Find Interesting

1. Solaris

Change the name in SVM

gurus, i have configured the LUN's in solaris 10.after labeled the disk,i have added the disk into one of the soft partition using metattach d0 c5t1000d10s6.actully before that i should confiure the powermt and than i should have add metattch d0 emcpowerc2.i forget to do that and increased... (0 Replies)
Discussion started by: rjay.com
0 Replies

2. Solaris

SVM, mirroring

Really sorry for the long posting. But i would really want to clear all the doubts. I have 2 disk c0t0d0 & c0t1d0, i wanted to mirror c0t1d0 (mirror) to c0t0d0 (main). Creating state database replica: metadb -a -c3 -f c0t0d0s7 ... (3 Replies)
Discussion started by: beginningDBA
3 Replies

3. UNIX for Dummies Questions & Answers

SVM doubt

i have taken two separate disk A and B created 4 slices in each A b s4 s4 s5 s5 s6 s6 s7 s7 took slices s4 of A and slice s6 0f B ---created a meta device d0 took slices s4 of B and slice s6 0f A---created a meta device d1 created main mirror d2 using d0... (1 Reply)
Discussion started by: vivek_ng
1 Replies

4. Solaris

Problem with SVM

HI, I added by error to a submirror some disks : metattach d53 c2t90d0s0 c2t90d1s0 ... instead of doing a stripe by disk (like that) : metattach d53 c2t90d0s0 metattach d53 c2t90d1s0 .. then, I did a growfs -M to expand FS and the size isn't correct. I tried to launch a... (1 Reply)
Discussion started by: phil.nakache
1 Replies

5. UNIX for Advanced & Expert Users

SVM

How to list out multiple Disk sets in SVM # metaset -s <disksetname> --- This will list out only one diskset but I need a list of disk sets configured for the node. Is there any command,please let me know ... Thanks in advance. (1 Reply)
Discussion started by: pramath
1 Replies

6. UNIX for Advanced & Expert Users

What is interlace value in SVM?

Hi All, I want to know what is the Interlace value in SVM and what is the need of this ? regards, prashant (1 Reply)
Discussion started by: prashant2507198
1 Replies

7. Solaris

SVM - Concatenation Question

Hi All, I have a metadevice d10 created on c0t0d0s7 in a sloaris machine. I have inserted a new disk and i would like to concatenate the new disk (c0t1d0s0) to d10. Since d10 is already in use,can i concatenate it? If so please help me with the command and procedure. I tried the... (2 Replies)
Discussion started by: Hari_Ganesh
2 Replies

8. Solaris

SVM Creation

Hello, I recently patched my Solaris 10 box and found out that few of the apps are not working. Fortunately, I had detached the mirroring prior to patching, so I just booted into my secondary disk and found that my apps are working.... The problem is this was way back in last month....see... (14 Replies)
Discussion started by: zigi_p5
14 Replies

9. Solaris

Fsck with SVM

Hello I want to ask that how to mount and run fsck in SVM disk.In my scenario if i have to disks c0t0d0 and c0t1d0 these two disks are in Mirroring (raid1) if i want to run fsck on the disks than below are the right steps? ok boot cdrom -s mount /dev/dsk/c0t0d0s0 /a cd /a fsck... (3 Replies)
Discussion started by: jhonnybravo
3 Replies

10. Solaris

SVM ISSUE...

Dear All, I face some errors in SVM.Need help. Actually couple of days ago i got a call from one of the customer mentioning that one of the sub-mirror was in Need maintance state. So we replaced that disk. After Replacing the disk it comes back to "Okay" State. But the Error are... (3 Replies)
Discussion started by: sudhansu
3 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 02:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy