Visit Our UNIX and Linux User Community

Operating Systems AIX IBM SAN STORAGE HOT SPARE DISK Post 302604167 by filosophizer on Saturday 3rd of March 2012 12:10:25 PM
Old 03-03-2012
[SOLVED] IBM SAN STORAGE HOT SPARE DISK

Hello,

I have DS4000 IBM SAN Storage ( aka FastT Storage )

One of my disks has failed and I had a hot spare disk covering all the arrays. As the disk failed, immediately the hotspare disk took over the failed disk ( see the JPEG in the attachment )

My Question: How can I make the hotspare which now took over the failed disk, to become part of the array and it should be a permanent disk ( instead of a hotspare disk as you can see + sign below the disk ) ?


thanks
IBM SAN STORAGE HOT SPARE DISK-hotsparejpg

Last edited by filosophizer; 03-14-2012 at 08:44 AM..
 
Test Your Knowledge in Computers #631
Difficulty: Medium
iPhone OS 1.0 was first released with great fanfare during the US Super Bowl in 2007.
True or False?

9 More Discussions You Might Find Interesting

1. AIX

IBM FastT600 SAN - RAID 5 Storage Manager Client v08.33.G5.03 - Recovery?

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

IBM SAN Storage DS4700 - Copy Mirror Flashcopy

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

Hot Spare pool

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

MPIO RDAC IBM SAN STORAGE DS4700 ?

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

Cannot see the IBM SAN storage

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

Hot Spare replacement

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

IBM SAN storage -- cache battery

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

IBM SAN TO SAN Mirroring

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

IBM AIX - SAN Storage DS4300 issue

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
volwatch(8)						      System Manager's Manual						       volwatch(8)

NAME
volwatch - Monitors the Logical Storage Manager (LSM) for failure events and performs hot sparing SYNOPSIS
/usr/sbin/volwatch [-m] [-s] [-o] [mail-addresses...] OPTIONS
Runs volwatch with the mail notification support to notify root (by default) or other specified users when a failure occurs. This option is started by default. Runs volwatch with hot spare support. Specifies an argument to pass directly to volrecover if it is running and hot spare support is enabled. DESCRIPTION
The volwatch command monitors LSM waiting for exception events to occur. When an exception event occurs, the volwatch command uses mailx(1) to send mail to: The root account. The user accounts specified when you use the rcmgr command to set the VOLWATCH_USERS variable in the /etc/rc.config.common file. The user account that you specify on the command line with the volwatch command. The volwatch command uses the volnotify command to wait for events to occur. When an event occurs, there is a 15 second delay before the failure is analyzed and the message is sent. This delay allows a group of related events to be collected and reported in a single mail message. By default, the volwatch command automatically starts when the system boots. You can enter the volwatch -s command to start the volwatch command with hot-spare support. Hot-spare support: Detects LSM events result- ing from the failure of a disk, plex, or RAID5 subdisk. Sends mail to the root account (and other specified accounts) with notification about the failure and identifies the affected LSM objects. Determines which subdisks to relocate, finds space for those subdisks in the disk group, relocates the subdisks, and notifies the root account (and other specified accounts) of these actions and their success or failure. When a partial disk failure occurs (that is, a failure affecting only some subdisks on a disk), redundant data on the failed portion of the disk is relocated and the existing volumes comprised of the unaffected portions of the disk remain accessible. Note Hot-sparing is only performed for redundant (mirrored or RAID5) subdisks on a failed disk. Non-redundant subdisks on a failed disk are not relocated, but you are notified of the failure. Only one volwatch daemon can be running on a system or cluster node at any time. Hot-sparing does not guarantee the same layout of data or the same performance after relocation. You may want to make some configuration changes after hot-sparing occurs. Mail Notification Support The following is a sample mail notification when a failure is detected: Failures have been detected by the Logical Storage Manager: failed disks: medianame ... failed plexes: plexname ... failed log plexes: plexname ... failing disks: medianame ... failed subdisks: subdiskname ... The Logical Storage Manager will attempt to find spare disks, relocate failed subdisks and then recover the data in the failed plexes. The following describes the sections of the mail message: The medianame list under failed disks specifies disks that appear to have com- pletely failed; The medianame list under failing disks indicates a partial disk failure or a disk that is in the process of failing. When a disk has failed completely, the same medianame list appears under both failed disks: and failing disks. The plexname list under failed plexes shows plexes that have been detached due to I/O failures experienced while attempting to do I/O to subdisks they contain. The plex- name list under failed log plexes indicates RAID5 or dirty region log (DRL) plexes that have experienced failures. The subdiskname list specifies subdisks in RAID5 volumes that have been detached due to I/O errors. Enabling Hot-Sparing By default, hot-sparing is disabled. To enable hot-sparing, enter the volwatch command with the -s option, for example: # volwatch -s To use hot-spare support you should configure a disk as a spare, which identifies the disk as an available site for relocating failed sub- disks. Disks that are identified as spares are not used for normal allocations unless you explicitly specify otherwise. This ensures that there is a pool of spare disk space available for relocating failed subdisks and that this disk space is not consumed by normal operations. Spare disk space is the first space used to relocate failed subdisks. However, if no spare disk space is available or if the available spare disk space is not suitable or sufficient, free disk space is used. You must initialize a spare disk and place it in a disk group as a spare before it can be used for replacement purposes. If no disks are designated as spares when a failure occurs, LSM automatically uses any available free disk space in the disk group in which the failure occurs. If there is not enough spare disk space, a combination of spare disk space and free disk space is used. When hot-sparing selects a disk for relocation, it preserves the redundancy characteristics of the LSM object to which the relocated sub- disk belongs. For example, hot-sparing ensures that subdisks from a failed plex are not relocated to a disk containing a mirror of the failed plex. If redundancy cannot be preserved using available spare disks and/or free disk space, hot-sparing does not take place. If relocation is not possible, mail is sent indicating that no action was taken. When hot-sparing takes place, the failed subdisk is removed from the configuration database and LSM takes precautions to ensure that the disk space used by the failed subdisk is not recycled as free disk space. Initializing and Removing Hot-Spare Disks Although hot-sparing does not require you to designate disks as spares, Compaq recommends that you initialize at least one disk as a spare within each disk group; this gives you control over which disks are used for relocation. If no spare disks exist, LSM uses available free disk space within the disk group. When free disk space is used for relocation purposes, it is likely that there may be performance degra- dation after the relocation. Follow these guidelines when choosing a disk to configuring as a spare: The hot-spare feature works best if you specify at least one spare disk in each disk group containing mirrored or RAID5 volumes. If a given disk group spans multiple controllers and has more than one spare disk, set up the spare disks on different controllers (in case one of the controllers fails). For a mirrored volume, the disk group must have at least one disk that does not already contain one of the volume's mirrors. This disk should either be a spare disk with some avail- able space or a regular disk with some free space. For a mirrored and striped volume, the disk group must have at least one disk that does not already contain one of the volume's mirrors or another subdisk in the striped plex. This disk should either be a spare disk with some available space or a regular disk with some free space. For a RAID5 volume, the disk group must have at least one disk that does not already contain the volume's RAID5 plex or one of its log plexes. This disk should either be a spare disk with some available space or a regular disk with some free space. If a mirrored volume has a DRL log subdisk as part of its data plex (for example, volprint does not list the plex length as LOGONLY), that plex cannot be relocated. Therefore, place log subdisks in plexes that contain no data (log plexes). By default, the volassist command creates log plexes. For mirroring the root disk, the rootdg disk group should contain an empty spare disk that satisfies the restrictions Although it is possible to build LSM objects on spare disks, it is preferable to use spare disks for hot-spare only. When relocating subdisks off a failed disk, LSM attempts to use a spare disk large enough to hold all data from the failed disk. To initialize a disk as a spare that has no associated subdisks, use the voldiskadd command and enter y at the following prompt: Add disk as a spare disk for newdg? [y,n,q,?] (default: n) y To initialize an existing LSM disk as a spare disk, enter: # voledit set spare=on medianame For example, to initialize a disk called test03 as a spare disk, enter: # voledit set spare=on test03 To remove a disk as a spare, enter: # voledit set spare=off medianame For example, to make a disk called test03 available for normal use, enter: # voledit set spare=off test03 Replacement Procedure In the event of a disk failure, mail is sent, and if volwatch was configured to run with hot sparing support with the -s option, volwatch attempts to relocate any subdisks that appear to have failed. This involves finding appropriate spare disk or free disk space in the same disk group as the failed subdisk. To determine which disk from among the eligible spare disks to use, volwatch tries to use the disk that is closest to the failed disk. The value of closeness depends on the controller, target, and disk number of the failed disk. For example, a disk on the same controller as the failed disk is closer than a disk on a different controller; a disk under the same target as the failed disk is closer than one under a different target. If no spare or free disk space is found, the following mail message is sent explaining the disposition of volumes on the failed disk: Relocation was not successful for subdisks on disk dm_name in volume v_name in disk group dg_name. No replacement was made and the disk is still unusable. The following volumes have storage on medianame: volumename ... These volumes are still usable, but the redundancy of those volumes is reduced. Any RAID-5 volumes with storage on the failed disk may become unusable in the face of further failures. If non-RAID5 volumes are made unusable due to the failure of the disk, the following is included in the mail message: The following volumes: volumename ... have data on medianame but have no other usable mirrors on other disks. These volumes are now unusable and the data on them is unavailable. These volumes must have their data restored. If RAID5 volumes are made unavailable due to the disk failure, the following message is included in the mail message: The following RAID-5 volumes: volumename ... have storage on medianame and have experienced other failures. These RAID-5 volumes are now unusable and data on them is unavailable. These RAID-5 volumes must have their data restored. If spare disk space is found, LSM attemps to set up a subdisk on the spare disk and use it to replace the failed subdisk. If this is suc- cessful, the volrecover command runs in the background to recover the contents of data in volumes on the failed disk. If the relocation fails, the following mail message is sent: Relocation was not successful for subdisks on disk dm_name in volume v_name in disk group dg_name. No replacement was made and the disk is still unusable. error message If any volumes (RAID5 or otherwise) are rendered unusable due to the failure, the following is included in the mail message: The following volumes: volumename ... have data on dm_name but have no other usable mirrors on other disks. These volumes are now unusable and the data on them is unavailable. These volumes must have their data restored. If the relocation procedure completes successfully and recovery is under way, the following mail message is sent: Volume v_name Subdisk sd_name relocated to newsd_name, but not yet recovered. Once recovery has completed, a message is sent relaying the outcome of the recovery procedure. If the recovery was successful, the follow- ing is included in the mail message: Recovery complete for volume v_name in disk group dg_name. If the recovery was not successful, the following is included in the mail message: Failure recovering v_name in disk group dg_name. SEE ALSO
mailx(1), rcmgr(8), voldiskadm(8), voledit(8), volintro(8), volrecover(8) volwatch(8)

Featured Tech Videos

All times are GMT -4. The time now is 11:47 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy