Home > Veritas Storage Foundation™ Volume Manager Manual Pages
VXUNRELOC (1M) |
|
Maintenance Commands |
Table of contents
vxunreloc - move a hot-relocated subdisk back to its original disk
/etc/vx/bin/vxunreloc
[-f]
[-g diskgroup]
[-n dm_name]
[-t tasktag] dm_name
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.
-
-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.
-
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 following 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'
If the operation fails,
vxunreloc
exits with a non-zero status.
A non-zero exit code is not a complete indicator of the problems encountered,
but rather denotes the first condition
that prevented further execution of the utility.
See
vxintro(1M)
for a list of standard exit codes.
vxassist(1M),
vxintro(1M),
vxmake(1M),
vxprint(1M),
vxrelocd(1M),
vxsd(1M),
vxsparecheck(1M)
Last updated: 31 Aug 2008
Copyright ©2009 Symantec Corporation
All rights reserved.