Sponsored Content
Full Discussion: break solaris mirror
Operating Systems Solaris break solaris mirror Post 302208745 by Perderabo on Tuesday 24th of June 2008 10:01:54 PM
Old 06-24-2008
Here is my procedure...it is a little bit clunky, but it works.

You should have the openboot variable "boot-device" set to something like
"disk0 disk1". You control which side you are booting from by explicitly
mentioning in the boot command at the ok prompt. Assuming that
disk0 c1t0d0
disk1 c1t1d0
is my root fs mirror...

Boot to single user mode from the installation CD.
ok boot -s cdrom

fsck root to ensure that everthing is ok and that you have the layout right
# fsck /dev/rdsk/c1t0d0

Then mount it
# mount /dev/dsk/c1t0d0 /a

Now, the only time that I use this procedure is when the root filesystem has been damaged to the point of not booting. So this is where I would fix it. But I am only fixing one side of the mirror. This is why I must now break the mirror. So assuming that I fixed the problem....

Edit /a/etc/system and remove the line that contains
rootdev

Edit /a/etc/vfstab and change
/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs ...
to
/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs ...

Then
cd /
umount /a
and get back to ok prompt (I just hit a break, but you may not be using a serial connection)

Boot into single user mode from the disk you just edited...
ok boot -s disk0

# metaclear -f -r d0
# init 0
ok boot disk0

And you should come up on one side of the mirror.

I have used this and it works for me. But it is a dangerous procedure. I
also doubt that my procedure is optimal. So proceed at your own risk. And again, I do this only on unbootable systems (or a test system to reherse).

There may be other slices still mirrored and I leave them that way. Once the box comes up, I then remirror root with the standard procedure.
 

9 More Discussions You Might Find Interesting

1. Solaris

Mirror solaris

Hi everyone. I have a Sun Solaris box which is running on only one internal disk and obviously that is not a good thing, if the disk should fail. This is a pritty straight forward operation in AIX, where my experties are. I have never done this in solaris and would therefore appriciate any help... (3 Replies)
Discussion started by: sprellari
3 Replies

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

3. HP-UX

Break mirror so that it can be used later

Hello again, We need to install patches to HP-UX B.11.11 but would like to break the mirror it has (with out damaging it) so that in case of failure we can use this a meassure procedure. Any ideas on how to do this Thank you! (2 Replies)
Discussion started by: AQG
2 Replies

4. Solaris

patch update and break mirror

Hi All, How do you know if you need to break the mirror on solaris 8 patch update? Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical. Is breaking a mirror a best practice only or really a requirement to some patch? Thanks, itik (1 Reply)
Discussion started by: itik
1 Replies

5. Solaris

Solaris Volume Manager: Break Mirror and use to make a 2nd machine

Hello: I have a machine built on 2 drives and mirrors have been created to a second set of 2 drives (4 total) on the same platform. SVM. Might anyone provide guidance to create a second machine by breaking the mirrored set, moving the two mirrors (2) to another machine (same platform type),... (1 Reply)
Discussion started by: 4dailyrunner
1 Replies

6. Linux

LVM - break mirror taking out orignal copy

Hi Guys, I have a mirrored LVM volume, and wish to break the mirror leaving only copy1 (effectively removing copy 0). Here's the config: # lvs -a -o +devices lvdata vg01 mwi-ao 2.19T lvdata_mlog 100.00 lvdata_mimage_0(0),lvdata_mimage_1(0) vg01... (0 Replies)
Discussion started by: badoshi
0 Replies

7. Solaris

Solaris patching using mirror disk backup? need help!

hi friends, need help.. it is my first time patching using mirror disk backup approach, not so sure about the steps :confused: how do you detach, patch it, boot it and reattach it ? any kind soul here can advise ? thanks in advance..:) below is the information from my machine: Filesystem ... (3 Replies)
Discussion started by: Exposure
3 Replies

8. Solaris

Healthy mirror on Solaris 10

Dear All I have question and I want some one to answer it .. in Solaris 10 I have two mirrors as below .. c3t0d0s0 & c3t1d0s0 NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ... (1 Reply)
Discussion started by: top.level
1 Replies

9. AIX

AIX break rootvg mirror from system down

Hello, aix 5.2, mirrored rootvg on hdisk0 and hdisk1. hdisk0 is dead. I can boot to cd, into sms, into maintenance mode. I can fsck all the various partitions on hdisk1 (the hd4 hd2 hd3, etc...) all is fine. But without the hdisk0 part of the mirror I cannot get the system to boot. ystem hangs on... (6 Replies)
Discussion started by: sshapiro
6 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 metadevice 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.11 9 Dec 2003 growfs(1M)
All times are GMT -4. The time now is 02:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy