21.02.2013 Views

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This error information displays the reason why the LV lvdb02 is marked stale.<br />

The hdisk4 had an DISK OPERATION ERROR and the LVDD could not write the<br />

mirror cache.<br />

Based on the information in the example, hdisk4 needs to be replaced. Before<br />

taking any action on the physical disk of the mirrored LV are recommended that<br />

you do a file system backup in case anything should go wrong. Since the other<br />

disk of the mirrored LV is still functional, all the data should be present. If the LV<br />

contains a database, then the respective database tools for backup of the data<br />

should be used.<br />

Removing a bad disk<br />

If the system is a high-availability (24x7) system, you might decide to keep the<br />

system running while performing the disk replacement, provided that the<br />

hardware supports an online disk exchange with hot-swappable disks. However,<br />

the procedure should be agreed upon by the system administrator or customer<br />

before continuing. Use the following steps to remove a disk:<br />

1. To remove the physical partition copy of the mirrored logical volume from the<br />

erroneous disk, use the rmlvcopy command as follows:<br />

# rmlvcopy lvdb02 1 hdisk4<br />

The logical volume lvdb02 is now left with only one copy, as shown in the<br />

following:<br />

# lslv -l lvdb02<br />

lvdb02:/u/db02<br />

PV COPIES IN BAND DISTRIBUTION<br />

hdisk3 500:000:000 21% 109:108:108:108:067<br />

2. Reduce the volume group by removing the disk you want to replace from its<br />

volume group:<br />

# reducevg -f mirrorvg hdisk4<br />

# lsvg -l mirrorvg<br />

mirrorvg:<br />

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT<br />

lvdb01 jfs 500 1000 2 open/syncd /u/db01<br />

lvdb02 jfs 500 500 1 open/syncd /u/db02<br />

loglv00 jfslog 1 1 1 open/syncd N/A<br />

3. Remove the disk as a device from the system and from the ODM database<br />

with the rmdev command:<br />

# rmdev -d -l hdisk4<br />

hdisk4 deleted<br />

This command is valid for any SCSI disk. If your system is using SSA, then an<br />

additional step is required. Since SSA disks also define the device pdisk, the<br />

146 <strong>IBM</strong> ^ Certification Study Guide - <strong>AIX</strong> <strong>5L</strong> <strong>Problem</strong> <strong>Determination</strong> Tools and Techniques

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!