Sponsored Content
Operating Systems Solaris Mirroring 2 disks with Solstice Disk Suite Post 302108705 by BOFH on Wednesday 28th of February 2007 11:39:00 AM
Old 02-28-2007
It doesn't matter. As long as the two partition sizes are the same, the disks will mirror. Heck, they can be different slices as long as the actual size of the slices match.

Carl
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Installing DISKS with Solaris Disk Suite

Hi, Ihave a Netra T1405 and would like to add 2 news disk (in mirror with SDS) in order to grow the size of the initial file system. The idea is to mount a new partition in order to setup new products... Could some one tell me the difrents steps to do this or give me links to documents. ... (1 Reply)
Discussion started by: guillaume35
1 Replies

2. Shell Programming and Scripting

Disk mirroring

Good Morning :) I have a new challenge to solve, I am going to write a new backup disk mirroring script. The current one, whcih is useing 'dd' caused some stalled systems :( Currently I am in the phase of experimenting with different methods, I was thinking about dump/restore afio/cpio or... (3 Replies)
Discussion started by: malcom
3 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 !! 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

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

6. Solaris

Solstice Disk Suite

I am doing disk mirroring and this command I entered: metainit d202 1 1 c0t1d0s0 gives me this error "metainit: d202: no such file or directory" The nmd value in /kernel/drv/md.conf is set to 2000. Any ideas what this error means? (3 Replies)
Discussion started by: bluridge
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. Solaris

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... (2 Replies)
Discussion started by: lm69a
2 Replies

10. 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
fmthard(1M)															       fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 08:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy