Sponsored Content
Full Discussion: Solaris 10 Disk Mirroring
Operating Systems Solaris Solaris 10 Disk Mirroring Post 302193004 by maddhadder71 on Thursday 8th of May 2008 08:54:08 AM
Old 05-08-2008
Here is what I use to mirror with Solaris Volume manager

# Setup the second disk (c1t1d0s2) to be identical as the primary (c1t0d0s2)
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2

# This creates the metadatabase - you need a free slice with 100mb, we use slice 7
metadb -a -f -c 3 c1t0d0s7
metadb -a -c 3 c1t1d0s7

# Setup Volumes on the primary for /, /var and swap
metainit -f d10 1 1 c1t0d0s0
metainit -f d11 1 1 c1t0d0s1
metainit -f d13 1 1 c1t0d0s3

# Setup Volumes on the secondary for /, /var and swap
metainit d20 1 1 c1t1d0s0
metainit d21 1 1 c1t1d0s1
metainit d23 1 1 c1t1d0s3

# Setup the mirrors
metainit d0 -m d10
metainit d1 -m d11
metainit d3 -m d13

# Make a backup of /etc/vfstab
cp /etc/vfstab /etc/vfstab.orig

# Make the boot disk boot from the mirror (this will modify the /etc/vfstab)
metaroot d0

# add entries for swap and var to /etc/vfstab ( make sure you rem out the old devices)
# Below is what the /etc/vfstab should look like
==================================================================================================
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
#/dev/dsk/c1t0d0s1 - - swap - no -
#/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no -
#/dev/dsk/c1t0d0s3 /dev/rdsk/c1t0d0s3 /var ufs 1 no -
/dev/md/dsk/d1 - - swap - no -
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no -
/dev/md/dsk/d3 /dev/md/rdsk/d3 /var ufs 1 no -
swap - /tmp tmpfs - yes -
===================================================================================================

# Run lockfs to clear and flush all data that is dirty.
lockfs -fa

# Halt system (you will now boot off the metadevices)
init 6

# Attach the submirrors
metattach d0 d20
metattach d1 d21
metattach d3 d23

metastat to check the status
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris mirroring / non-root disk

Hi Guys, Need to add 2 disks into a JBOD array (3310). Does anyone see anything wrong with my Procedure / Doco below? 1> Logon to system, check system logs for abnormal entries. 2> Make backups of related system files: A>cp -p /etc/system /etc/system.backup.081505 B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. UNIX for Advanced & Expert Users

Solaris 8 disk/mirroring issue

Hello! I recently inherited system administration duties for a SUN v880 box. The system has 6 physical hard disks.. In doing some basic maintenance, I found they're configured for mirroring. I ran the metastat and metadb commands, and many of the mirrors are showing they are in need of... (5 Replies)
Discussion started by: ghuber
5 Replies

3. Solaris

Disk mirroring

Hi I have two raw disk that I want to mirror and then create soft partition on that. Could someone please help in the steps required c0t1d0 c0t0d0 Thanks Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies

4. Solaris

[HELP] mirroring disk at solaris 8 sparc v890

hi expert, sorry i'm new in solaris system, need more advice and help :) i'm confusing with mirroring disk at my sparc v890 solaris 8, i have 6 harddisk which the structure shown below : format : AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> ... (4 Replies)
Discussion started by: bucci
4 Replies

5. Solaris

Help !! disk Mirroring

Hi I have a Sunfire X4100 box with a 4 disk Chassis (although I only have 2 disks in it). I have been asked to add two more disks into the chassis so that I can mirror the original two using SVM .....Ive read through a couple of SVM docs but am finding it a little confusing, and if any of you... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

6. Solaris

Disk Mirroring for Solaris 10 x86

I am having an issue with setting up disk mirroring for Solaris 10 on an x86 server. My main problem is that the volumes and slices have already been setup and our proprietary software has already been installed and configured. The entire drive has been allocated in this configuration and the... (2 Replies)
Discussion started by: chuck43
2 Replies

7. Solaris

Disk Mirroring on solaris 5.8

Hi Friends, I am having Sun Solaris 5.8 OS installed having 2 different size hard disk, sizes are c0t0d0s0(160 GB) and c0t2d0s0 (40GB). I have installed Sun Solaris 5.8 OS in c0t0d0s0 (160GB) harddisk. I have configured all the parameters required for disk mirroring. But when executing... (4 Replies)
Discussion started by: Vijayakumarpc
4 Replies

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

9. Red Hat

Disk Mirroring

Hi, How to identify whether the disk is being mirrored or not in RHEL (2 Replies)
Discussion started by: gsiva
2 Replies

10. Solaris

Root disk mirroring in Solaris 10

I would like to perform root disk mirroring task. Can someone please help me out on this. Thanks !! Regards, Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
growfs(1M)						  System Administration Commands						growfs(1M)

NAME
growfs - non-destructively expand a UFS file system SYNOPSIS
/usr/sbin/growfs [-M mount-point] [newfs-options] [raw-device] DESCRIPTION
growfs non-destructively expands a mounted or unmounted UNIX file system (UFS) to the size of the file system's slice(s). Typically, disk space is expanded by first adding a slice to a metadevice, then running the growfs command. When adding space to a mirror, you expand each submirror before expanding the file system. growfs will ``write-lock'' (see lockfs(1M)) a mounted file system when expanding. The length of time the file system is write-locked can be shortened by expanding the file system in stages. For instance, to expand a 1 Gbyte file system to 2 Gbytes, the file system can be grown in 16 Mbyte stages using the -s option to specify the total size of the new file system at each stage. The argument for -s is the number of sectors, and must be a multiple of the cylinder size. Note: The file system cannot be grown if a cylinder size of less than 2 is specified. Refer to the newfs(1M) man page for information on the options available when growing a file system. growfs displays the same information as mkfs during the expansion of the file system. If growfs is aborted, recover any lost free space by unmounting the file system and running the fsck command, or run the growfs command again. OPTIONS
Root privileges are required for all of the following options. -M mount-point The file system to be expanded is mounted on mount-point. File system locking (lockfs) will be used. newfs-options The options are documented in the newfs man page. raw-device Specifies the name of a raw metadevice or raw special device, residing in /dev/md/rdsk, or /dev/rdsk, respectively, including the disk slice, where you want the file system to be grown. EXAMPLES
Example 1: Expanding nonmetadevice slice for /export file system The following example expands a nonmetadevice slice for the /export file system. In this example, the existing slice, /dev/dsk/c1t0d0s3, is converted to a metadevice so additional slices can be concatenated. # metainit -f d8 2 1 c1t0d0s3 1 c2t0d0s3 # umount /export Example 2: Associate /export with new metadevice Edit the /etc/vfstab file to change the entry for /export to the newly defined metadevice, d8. # mount /export # growfs -M /export /dev/md/rdsk/d8 The first example starts by running the metainit command with the -f option to force the creation of a new concatenated metadevice d8, which consists of the existing slice /dev/dsk/c1t0d0s3 and a new slice /dev/dsk/c2t0d0s3. Next, the file system on /export must be unmounted. The /etc/vfstab file is edited to change the entry for /export to the newly defined metadevice name, rather than the slice name. After the file system is remounted, the growfs command is run to expand the file system. The file system will span the entire metade- vice when growfs completes. The -M option enables the growfs command to expand a mounted file system. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 3: Dynamic Expansion of /export file system The following example picks up from the previous one. Here, the /export file system mounted on metadevice d8 is dynamically expanded. # metattach d8 c0t1d0s2 # growfs -M /export /dev/md/rdsk/d8 This example begins by using the metattach command to dynamically concatenate a new slice, /dev/dsk/c0t1d0s2, to the end of an existing metadevice, d8. Next, the growfs command specifies that the mount-point is /export and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d8. The file system will span the entire metadevice when growfs completes. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 4: Expanding mounted file system to existing mirror The following example expands a mounted file system /files, to an existing mirror, d80, which contains two submirrors, d9 and d10. # metattach d9 c0t2d0s5 # metattach d10 c0t3d0s5 # growfs -M /files /dev/md/rdsk/d80 In this example, the metattach command dynamically concatenates the new slices to each submirror. The metattach command must be run for each submirror. The mirror will automatically grow when the last submirror is dynamically concatenated. The mirror will grow to the size of the smallest submirror. The growfs command then expands the file system. The growfs command specifies that the mount-point is /files and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d80. The file system will span the entire mirror when the growfs command completes. During the expansion, write access for the file system is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), lockfs(1M), mkfs(1M), metattach(1M), newfs(1M), attributes(5) Solaris Volume Manager Administration Guide LIMITATIONS
Only UFS file systems (either mounted or unmounted) can be expanded using the growfs command. Once a file system is expanded, it cannot be decreased in size. The following conditions prevent you from expanding file systems: When acct is activated and the accounting file is on the target device. When C2 security is activated and the logging file is on the target file system. When there is a local swap file in the target file system. When the file system is root (/), /usr, or swap. SunOS 5.10 9 Dec 2003 growfs(1M)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy