05-16-2011
If all else fails you could always assign a new 300GB LUN to the VG, use migratepv to migrate from original disk to new and then you can take the original disk away (after doing reducevg of course).
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi,
i have a volume on a LUN of an EMC-storage and i need to increase the
size.
i could increase the size of the LUN on the EMC, i could increase the
size of the disk for solaris, but how can i tell the veritas volume
manager that the disk is larger now?
what i've done:
1. LUN on EMC
2.... (3 Replies)
Discussion started by: pressy
3 Replies
2. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
3. AIX
Hi,
I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size.
How can I get the OS to see the additional 50GB?
---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies
4. Solaris
Hi,
I need to set up iscsi LUN on Solaris 9. I've done it on Solaris 10 with iscsiadm. How do you do it on Solaris 9 though? Currently using Solaris 9 update 2. Your help is appreciated.
Thanks,
Sparcman (6 Replies)
Discussion started by: sparcman
6 Replies
5. Solaris
We "lose" the iscsi device after a reboot - i.e., it appears in /dev/rdsk and /dev/dsk but format cannot find it. Obviously, it won't mount either. This happens for two separately defined luns.
We must be missing a step in iscsiadm.
The luns are defined as targets, we can see them in... (2 Replies)
Discussion started by: jim mcnamara
2 Replies
6. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
7. Red Hat
Hi,
I have a SAN LUN of 550 GB created as an ext3 partition of the entire lun and need to make the lun and partition larger... 600 GB
# fdisk -l /dev/sdj
Disk /dev/sdj: 590.5 GB, 590558003200 bytes
255 heads, 63 sectors/track, 71797 cylinders
Units = cylinders of 16065 * 512 = 8225280... (3 Replies)
Discussion started by: jamba1
3 Replies
8. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
9. Red Hat
Hi,
I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is :
node 1 shows the shared iscsi lun as sdc
node 2 shows the same as sdg (changes on reboots)
Due to this (i guess) i get i/o error & i can not read files created by... (0 Replies)
Discussion started by: heman96
0 Replies
10. Solaris
trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try... (2 Replies)
Discussion started by: os2mac
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)