09-15-2011
replacing mirror disk
Hi Admins,
I am new into aix.I was surfing aix pages and reading how to replace failed mirror disks.I read in one of the posts that we have to reboot the server to replace the disk. actually i was a HPUX admin and many times replaced root mirror disk online.Ofcourse it was hot swappable.
Now i have not checkd my aix disks are hot swappable or not.and OS version is 5.3. Need i reboot server to replace disk in aix 5.3.. please explain in detail.
Regards
newaix
10 More Discussions You Might Find Interesting
1. HP-UX
Being somewhat extremely new to Unix, I have just had a system crash
One of my Volume Groups has crashed
However, this Volume Group is actually mirrored
How do I switch to use the mirrored copy?
Any assistance greatly appreciated
Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies
2. Solaris
Hi,
need some help.
I’m new to solaris and trying to find out how to mirror a data disk (not the root disk).
In AIX it is easy but with solaris 5.8 I don’t find my way even with the SUN docs (disk/suide is installed).
What is behind is I want to migrate a disk from 1 storage system to... (7 Replies)
Discussion started by: ccTester
7 Replies
3. Solaris
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Discussion started by: simquest
1 Replies
4. Filesystems, Disks and Memory
I have a SUN 440 running Solaris 8 that is generating funny errors on /dev/dsk/c1t0d0 and I would like to dupe the drive(the non offending drives are removed for this process), swap it with the dupe and reboot. From what I have read, the process seems simple:
dd if=/dev/dsk/c1t0d0... (1 Reply)
Discussion started by: hardyj
1 Replies
5. UNIX for Dummies Questions & Answers
hi.. newbie here, just wonder why there is a need for mirroring in some servers whereby we already had backups by cron jobs ? (4 Replies)
Discussion started by: Exposure
4 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
8. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
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. Solaris
Hi All
BAsed on the below I would like to verifu two things
(1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up)
(2) the Procedure for renewal
# df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
LEARN ABOUT HPUX
vxunreloc
vxunreloc(1M) vxunreloc(1M)
NAME
vxunreloc - move a hot-relocated subdisk back to its original disk
SYNOPSIS
/etc/vx/bin/vxunreloc [-f] [-g diskgroup] [-n dm_name] [-t tasktag] dm_name
DESCRIPTION
The Veritas Volume Manager (VxVM) hot-relocation feature can detect an I/O failure in a subdisk, relocate the subdisk, and recover the plex
associated with the subdisk. vxunreloc lets you reverse the process and move the hot-relocated subdisks back onto a disk that was replaced
after a disk failure.
dm_name specifies the disk where the hot-relocated subdisks originally resided. The -n option moves the subdisks to a different disk from
where VxVM originally relocated them. For example, when disk03 fails, all the subdisks residing on it are hot-relocated to other disks.
After the disk is repaired, it is added back to the disk group using a different name, for example, disk05. If you wanted to move all the
hot-relocated subdisks back to the repaired disk, you would enter:
/etc/vx/bin/vxunreloc -n disk05 disk03
When vxunreloc moves the hot-relocated subdisks, it moves them to their original offsets. However, if there was a subdisk that occupied
part or all of the area on the destination disk, vxunreloc prints an error message and exits. In this situation, you can use the -f option
to unrelocate the subdisks to a specified disk, but not to their original offsets.
OPTIONS
-f Unrelocates a subdisk to a different offset if unrelocating to the original offset is not possible.
-g diskgroup
Unrelocates a subdisk from the specified disk group. If this option is not specified, the default disk group is determined using
the rules given in the vxdg(1M) manual page.
-n dm_name
Specifies a new disk name to relocate to a disk with a different name.
-t tasktag
Specifies a tag to pass to the underlying utility.
SUBDISK RECORD FIELDS
orig_dmname
When a subdisk is hot-relocated, its original disk media name is stored in the orig_dmname field. When you run the vxunreloc
command to move the subdisk back to the original disk (or to a new disk), this field is cleared. Before you run the vxunreloc
command, you can do a search on this field to determine the subdisks that originated from a failed disk. For example, the fol-
lowing command lists all the subdisks that were hot-relocated from mydg01 in the disk group mydg. Note that you must prefix the
field name with "sd_" for the command to work.
vxprint -g mydg -se 'sd_orig_dmname="mydg01"'
orig_dmoffset
When a subdisk is hot-relocated, its offset into the original disk is stored in the orig_dmoffset field. When you run vxunreloc
to move the subdisk to the original disk, or to a new disk, this field is zeroed. The following command lists a hot-relocated
subdisk which originally resided at disk10 at offset 1000. Again note that you must prefix the field names with "sd_" for the
command to work.
vxprint -g dg01 -se 'sd_orig_dmname="disk10"
&& sd_orig_dmoffset=1000'
EXIT CODES
If the operation fails, vxunreloc exits with a non-zero status. A non-zero exit code is not a complete indicator of the problems encoun-
tered, but rather denotes the first condition that prevented further execution of the utility.
See vxintro(1M) for a list of standard exit codes.
SEE ALSO
vxassist(1M), vxintro(1M), vxmake(1M), vxprint(1M), vxrelocd(1M), vxsd(1M), vxsparecheck(1M)
VxVM 5.0.31.1 24 Mar 2008 vxunreloc(1M)