Sponsored Content
Operating Systems Solaris Mirroring using non-identical disks Post 302498528 by lm69a on Monday 21st of February 2011 05:05:25 PM
Old 02-21-2011
Mirroring using non-identical disks

I've been testing mirroring root partitions for the past few days within a virtual environment and on an old ML350. However, the live system that this is practice for has two disks, and they're non-identical.

I've done a bit of searching through the forum and see that a lot of people recommend just calculating the partitions for the second disk manually. However, I'm a bit of a noob when it comes to doing so, so was wondering if somebody could offer any advice/help.

Here are the two partition tables as they are at the moment:

Disk 1 (i.e. the live disk):

Code:
bash-3.00# prtvtoc /dev/rdsk/c1t0d0s2
* /dev/rdsk/c1t0d0s2 partition map
*
* Dimensions:
*     512 bytes/sector
*      63 sectors/track
*     255 tracks/cylinder
*   16065 sectors/cylinder
*    8940 cylinders
*    8938 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
* Unallocated space:
*       First     Sector    Last
*       Sector     Count    Sector
*   143315865    273105 143588969
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00    8418060  67119570  75537629   /
       1      3    01      16065   8401995   8418059
       2      5    00          0 143588970 143588969
       3      0    00   75537630  33993540 109531169
       6      0    00  109531170  33559785 143090954
       7      0    00  143090955    224910 143315864
       8      1    01          0     16065     16064

Disk 2 (the soon to be mirror):

Code:
bash-3.00# prtvtoc /dev/rdsk/c1t1d0s2
* /dev/rdsk/c1t1d0s2 partition map
*
* Dimensions:
*     512 bytes/sector
*     911 sectors/track
*       2 tracks/cylinder
*    1822 sectors/cylinder
*   13217 cylinders
*   13215 accessible cylinders
*
* Flags:
*   1: unmountable
*  10: read-only
*
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      2    00       1822    262368    264189
       1      3    01     264190    262368    526557
       2      5    01          0 143487966 143487965
       6      4    00     526558 142957764 143484321

       8      1    01          0      1822      1821

Notice somebody's failed attempt - ominous!

Firstly - am I right in thinking the disks are (on paper) roughly equal in size (i.e. they share a similar number of sectors, and are both 512bytes/sector)?

Secondly, will prtvtoc/fmthard use the sector positions rather than the cylinder counts when labelling the new disk? Because if so am I right in thinking that the unallocated space on the end of c1t1d0 should mean that a straight copy of the VTOCs between disks is possible? (That is, the current disk's assigned partitions don't overflow past the new disks available sectors?)

Any advice would be greatly appreciated - I can only test so much, and unfortunately this part can only be tested on the live system because I don't have unequal disks to test with Smilie

Last edited by lm69a; 02-21-2011 at 09:38 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to check the files are Identical or not?

Hi, I am taking backup in every hr and every day, I want to programmatically check my backup files are identical with original files. Any methods are available in Unix scripts? Any idea.? I don't want to download both and compare, I looking for idea to develop a script to read both files and... (3 Replies)
Discussion started by: redlotus72
3 Replies

2. Solaris

Mirroring 2 disks with Solstice Disk Suite

hello everybody, I have a system in Solaris 8 with SDS 4.2.1 I need to mirror the system disk which has the following characteristics : * /dev/rdsk/c0t0d0s2 partition map * * Dimensions: * 512 bytes/sector * 133 sectors/track * 27 tracks/cylinder * 3591 sectors/cylinder... (3 Replies)
Discussion started by: aribault
3 Replies

3. UNIX for Dummies Questions & Answers

du -s -k differences between two identical directories

I tarred a directory from a linux server to a solaris server. When I do a du -s -k on the directory, I get almost 150k difference in the file sizes. If I do a ls | wc -l, it is the same. If I look at the size of the individual files, it is the same. I did an ls on the 2 directories and... (6 Replies)
Discussion started by: csgonan
6 Replies

4. Linux

How to set up mirroring on OS disks.

Hi. I have a SLES10 machine which until recently had only one disk. Now there is a second disk which I would like to mirror my OS installation to. I have three partitions, first one for /boot (~100M), the second one for / (~1G) and then the rest as a LVM partition with several volumes under... (0 Replies)
Discussion started by: Sprellarinn
0 Replies

5. Shell Programming and Scripting

Ignore identical lines

Hello Experts, I have two files called "old" and "new". My old file contains 10 lines and my new file contains 10 + "n" lines. The first field in both these files contain ID. I sort these two files on ID. I am interested in only the lines that are in the new file and not in old. I tried... (4 Replies)
Discussion started by: forumthreads
4 Replies

6. Shell Programming and Scripting

to get two almost identical rows into one

Hi All, I am having hard time in getting two almost identical rows into one, I know how to do if starting word is unique, anyhow this is my problem Input File: issue1 5167 dum 1 1 kkk 7888 dum 2 1 ffff 7888 dum 2 2 llll 7888 dum 3 1 eee 7888 issue2 7667 dum 2 1 jjjj 8999 dum 2 2 jjjj... (3 Replies)
Discussion started by: ricky315
3 Replies

7. Solaris

Provide examples- 4 disks (3 way mirroring)

Hi, need some guidance, maybe I don't understand the term 3 or 4 way mirror. I have 4 disks. All of same capacity. Need to 3-way mirror the disks for the OS using SVM (4 Replies)
Discussion started by: incredible
4 Replies

8. Solaris

Disk mismatch while trying to zfs mirroring non-root disks

Hello All, I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me. --- iostat command shows the disk to be similiar --- format command shows disk to be different :confused: --- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies

9. UNIX for Dummies Questions & Answers

more than 10 identical lines

I have a file that looks like this 10 user1s, 5 user2s and 10 users3. 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.1 user1 10.10.1.2 user2 10.10.1.2 user2 10.10.1.2 user2... (7 Replies)
Discussion started by: lawsongeek
7 Replies

10. Ubuntu

reinstall identical system?

I have my Ubuntu system nicely tailored to my needs, with specific software installed, and other things removed. I'd like to build a new PC, and have the identical software configuration on it. Is there some easy way to export the list of installed software to a file? Then have the new machine... (3 Replies)
Discussion started by: lupin..the..3rd
3 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 01:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy