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.

<strong>AIX</strong> version level<br />

Verify that the volume group you are importing is supported by the level of <strong>AIX</strong><br />

running on the system. Various new features have been added to the LVM<br />

system at different levels of <strong>AIX</strong>, such as support for large volume groups. A<br />

number of these features require a change to the format of the VGDA stored on<br />

the disk, and thus will not be understood by previous levels of <strong>AIX</strong>.<br />

Invalid PVID<br />

Check that all of the disks in the volume group you are trying to import are<br />

marked as available to <strong>AIX</strong> and have valid PVIDs stored in the ODM. This can be<br />

checked using the lspv command. If any disks do not have a PVID displayed,<br />

use the chdev command to resolve the problem. For example:<br />

# lspv<br />

hdisk0 000bc6fdc3dc07a7 rootvg<br />

hdisk1 000bc6fdbff75ee2 testvg<br />

hdisk2 000bc6fdbff92812 testvg<br />

hdisk3 000bc6fdbff972f4 None<br />

hdisk4 None None<br />

# chdev -l hdisk4 -a pv=yes<br />

hdisk4 changed<br />

# lspv<br />

hdisk0 000bc6fdc3dc07a7 rootvg<br />

hdisk1 000bc6fdbff75ee2 testvg<br />

hdisk2 000bc6fdbff92812 testvg<br />

hdisk3 000bc6fdbff972f4 None<br />

hdisk4 000bc6fd672864b9 None<br />

In this example, the PVID for hdisk4 is not shown by the lspv command. This is<br />

resolved by running the chdev command. The PVID is read from the disk and<br />

placed in the ODM, if the disk is accessible. It will only write a new PVID if there<br />

truly is no PVID on the disk. Alternately, the disk can be removed using the<br />

rmdev command and, by running the configuration manager cfgmgr command,<br />

the device is recreated with the correct PVID. After this, an import of the volume<br />

group with the importvg command should be possible.<br />

Disk change while volume group was exported<br />

If the importvg command fails with an error message similar the following, the<br />

physical volume is marked missing and it is possible that some disk change to<br />

the disks defined in the volume group was made while the volume group was<br />

exported:<br />

0516-056 varyon testvg: The volume group is not varied on because a<br />

physical volume is marked missing. Run diagnostics.<br />

142 <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!