03-03-2012
a quick question:
I have one free disk plugged in the SAN Storage. It is not part of any array or hotspare coverage ( I have removed it from hotspare coverage -- )
Can I just remove the disk while the SAN is powered on and plugged into the failed disk ?
or
Do I need to shutdown the SAN Storage and remove the disk ?
--------------------
SOLUTION:
1) You can remove / unplug an ununsed powered Disk from the SAN STORAGE and use it in place of failed disk without powering off or anything
2) You can make the HOTSPARE a permanent disk provided this option is supported by the firmware level and software of DS4000
Last edited by filosophizer; 03-14-2012 at 08:44 AM..
9 More Discussions You Might Find Interesting
1. AIX
To summarize the problem: The "IBM FastT Storage Manager Client v8" shows that our Disk Farm is arranged into 6 logical drives each in a RAID 5 configuration. This software also shows that 5 of the 6 logical drives (from Disk Farm) are in a error state: "Failed Logical Drive - Drive Failure".... (1 Reply)
Discussion started by: aix-olympics
1 Replies
2. AIX
Hello,
Does anyone know how to copy SAN Storage logical disks from IBM TotalStorage Software.
I have a SAN Logical Disk of 200GB mounted on my AIX LPAR_1 via fibre channel fcs0
I would like to make an exact copy of the SAN Logical Disk from IBM totalStorage and mount it on AIX LPAR_2
... (4 Replies)
Discussion started by: filosophizer
4 Replies
3. Solaris
One more query in SVM :) Now with hot spare spool...
I can understand adding/replacing a slice in particular hot spare pool with "-a / -r" option (or) adding a slice to all existing hot spare pool with "-all" option. Here my query is for deleting, we have only option "-d".
1) If the hot... (2 Replies)
Discussion started by: gowthamakanthan
2 Replies
4. AIX
Hello,
I have AIX 6.1 with TL 4 and it is connected to IBM SAN STORAGE DS4700
After assigning some disks from SAN to AIX, I can see the disks in my AIX as
hdisk2 Available 05-00-02 MPIO Other DS4K Array Disk
hdisk3 Available 05-00-02 MPIO Other DS4K Array Disk
But it should... (0 Replies)
Discussion started by: filosophizer
0 Replies
5. Solaris
HI all,
I had recently change the Server storage from EMC to the IBM SAN.
but after the configuration, the IBM success to see the server HBA port and successfully assign a LUN for the server.
When i go to the server, and restarted it. i use the "format" command to check, but din see any... (1 Reply)
Discussion started by: SmartAntz
1 Replies
6. Solaris
Hi Guys,
Can Someone pls let me know the thorough process for Hot spare replacement
as current Hot spare slice has broken down . :mad:
Thanks
---------- Post updated at 06:34 PM ---------- Previous update was at 05:21 PM ----------
Update : Its a solaris 10 box (1 Reply)
Discussion started by: Solarister
1 Replies
7. AIX
Hello,
I have IBM SAN STORAGE DS4100 and one of the cache battery for the controller is dead. Suddenly the performance has been degraded and access to SAN disks ( reading and writing ) became very slow ?
My query: Replacing the battery will take 6 days, so in the mean time what are the ways... (1 Reply)
Discussion started by: filosophizer
1 Replies
8. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
9. AIX
Hi,
This is follow up to the post https://www.unix.com/aix/233361-san-disk-appearing-double-aix.html
When I connected Pseries Machine HBA Card ( Dual Port ) directly to the SAN Storage DS4300 , I was able to see Host Port Adapter WWN numbers , although I was getting this message... (2 Replies)
Discussion started by: filosophizer
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)