12-03-2010
Quote:
Originally Posted by
jalite19
[...]But when I look at the partition table of hdisk32 and hdisk3, they are not the same [...] How can I fix this without offlining extvg?
- As you have an hdisk32 and an hdisk55 I assume that these are not physical disks but SAN disks. In this case the information of the LV position is completely useless because you have no information about where the data is being placed on the LUN's underlying physical disk(s).
- If you use physical disks having different layouts on different disks might be an advantage if you have more read than write operations because the disk's head will start reading data from that copy that can be accessed first (as long as you don't configure your LV's otherwise). If you use exact mapping the head move will allways be the same.
- The layout of the two disks is different because there was space used on hdisk32 before /db/arch had been created. This space has been freed and neither been used by another LV/FS nor filled via a reorgvg.
- Creating the mirror with exact mapping is the fastest possibility to make the mapping the same on every disk. In case the disk's characteristics are identical you might also try a reorgvg. There are even other ways to achieve this. All share that you can change this on the fly. LVM is great.
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
First post, I work as database developer (Oracle)
My task is to setup a solaris system on a VMware installation which sits on a x86 server.
I have installed the Os, applied patches (I think) and on VMWARE I added new hardware (Disk) which is where my database will be.
The... (5 Replies)
Discussion started by: platforminc
5 Replies
2. Solaris
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies
3. Solaris
Solaris 10 5/08 on Ultra 40 M2
It boots fine off primary disk but having issues booting off the mirror disk.
I get this error when booting off mirror disk:
Booting 'Solaris 10 ... Mirror disk'
root (hd1,0,a)
Error 22: No such partition
Press any key to continue...
Any... (7 Replies)
Discussion started by: etc
7 Replies
4. Solaris
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies
5. UNIX for Advanced & Expert Users
I apologize is this isn't an appropriate post for the 'advanced' UNIX, so please let me know if I should post this under UNIX for dummies, but here's my problem in a nutshell: I having problems creating a mirrored logical volume.
I have created two new physical volumes
... (2 Replies)
Discussion started by: simonrodan
2 Replies
6. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
7. UNIX for Advanced & Expert Users
Hi,
I am trying to get the position of a repeated string in a line using
grep -b -o "pattern"
In my server I am using GNU grep version 2.14 and the code is working fine. However when I am deploying the same code in a different server which is using GNU grep version 2.5.1 the code is not... (3 Replies)
Discussion started by: Subhamoy
3 Replies
8. Shell Programming and Scripting
I've created a pretty straightforward shell script to do backups via rsync. Every night it rsyncs a copy of a website (approx 60GB) to the local machine. Once a week, after the rsync step, it zips the local copy of the whole site into 2GB chunks and places them in another folder.
When running... (3 Replies)
Discussion started by: Agreppa
3 Replies
9. Solaris
Hello all,
i have the mirror disk problem with SunOS 5.10.
here's the message:
# metastat d15
d15: Mirror
Submirror 0: d16
State: Needs maintenance
Submirror 1: d17
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel... (4 Replies)
Discussion started by: rwprabowo
4 Replies
10. Red Hat
hi
I created a new partition
ls -l /dev/sda*
brw-rw---- 1 root disk 8, 0 Oct 21 12:29 /dev/sda
brw-rw---- 1 root disk 8, 1 Oct 12 11:19 /dev/sda1
brw-rw---- 1 root disk 8, 10 Oct 21 13:50 /dev/sda10
brw-rw---- 1 root disk 8, 2 Oct 12 11:19 /dev/sda2
brw-rw---- 1 root disk 8, 3 Oct... (3 Replies)
Discussion started by: mnnn
3 Replies
LEARN ABOUT LINUX
metareplace
metareplace(1M) System Administration Commands metareplace(1M)
NAME
metareplace - enable or replace components of submirrors or RAID5 metadevices
SYNOPSIS
/usr/sbin/metareplace -h
/usr/sbin/metareplace [-s setname] -e mirror component
/usr/sbin/metareplace [-s setname] mirror component-old component-new
/usr/sbin/metareplace [-s setname] -e RAID component
/usr/sbin/metareplace [-s setname] [-f] RAID component-old component-new
DESCRIPTION
The metareplace command is used to enable or replace components (slices) within a submirror or a RAID5 metadevice.
When you replace a component, the metareplace command automatically starts resyncing the new component with the rest of the metadevice.
When the resync completes, the replaced component becomes readable and writable. If the failed component has been hot spare replaced, the
hot spare is placed in the available state and made available for other hot spare replacements.
Note that the new component must be large enough to replace the old component.
A component may be in one of several states. The Last Erred and the Maintenance states require action. Always replace components in the
Maintenance state first, followed by a resync and validation of data. After components requiring maintenance are fixed, validated, and
resynced, components in the Last Erred state should be replaced. To avoid data loss, it is always best to back up all data before replacing
Last Erred devices.
OPTIONS
Root privileges are required for all of the following options except -h.
-e Transitions the state of component to the available state and resyncs the failed component. If the failed component has
been hot spare replaced, the hot spare is placed in the available state and made available for other hot spare replace-
ments. This command is useful when a component fails due to human error (for example, accidentally turning off a disk), or
because the component was physically replaced. In this case, the replacement component must be partitioned to match the
disk being replaced before running the metareplace command.
-f Forces the replacement of an errored component of a metadevice in which multiple components are in error. The component
determined by the metastat display to be in the ``Maintenance'' state must be replaced first. This option may cause data to
be fabricated since multiple components are in error.
-h Display help message.
-s setname Specifies the name of the diskset on which metareplace will work. Using the -s option will cause the command to perform its
administrative function within the specified diskset. Without this option, the command will perform its function on local
metadevices.
mirror The metadevice name of the mirror.
component The logical name for the physical slice (partition) on a disk drive, such as /dev/dsk/c0t0d0s2.
component-old The physical slice that is being replaced.
component-new The physical slice that is replacing component-old.
RAID The metadevice name of the RAID5 device.
EXAMPLES
Example 1: Recovering from Error Condition in RAID5 Metadevice
This example shows how to recover when a single component in a RAID5 metadevice is errored.
# metareplace d10 c3t0d0s2 c5t0d0s2
In this example, a RAID5 metadevice d10 has an errored component, c3t0d0s2, replaced by a new component, c5t0d0s2.
Example 2: Use of -e After Physical Disk Replacement
This example shows the use of the -e option after a physical disk in a submirror (a submirror of mirror d11, in this case) has been
replaced.
# metareplace -e d11 c1t4d0s2
Note: The replacement disk must be partitioned to match the disk it is replacing before running the metareplace command.
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
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4),
mddb.cf(4), md.tab(4), attributes(5), md(7D)
Solaris Volume Manager Administration Guide
SunOS 5.10 8 Aug 2003 metareplace(1M)