Other problems

Description

Problems with detecting hardware such as SCSI cards or LAN cards.

Explanation

Problems when using an ASUS PR-DL533 motherboard: Linux does not detect hardware correctly. It is a known problem of the Linux ACPI subsystem that it does not work correctly with some motherboards. If specifying the general acpi=off option, it is possible that the ACPI subsystem does not detect the hardware (on-board network card, SCSI card) correctly.

Workaround

Specify the following boot parameters:
acpi=oldboot pci=noacpi apm=power-off

Description

If you check for potential inconsistencies between a File System Catalog (FSC) and Fast Recovery Information (FRI) data on the corresponding OA media, the following lines may be present in the output of the ivdcheck --fsc-media <PartitionName> command:
DUMP: FSC FRI Notes
MigSize <SizeInFSC> <SizeInFRI> MISMATCH
MigFlags <FlagsInFSC> <FlagsInFRI> MISMATCH
The MISMATCH keywords indicate inconsistencies. After you invoke the command ivdcheck --fsc-media <PartitionName> --autocorrect to solve the underlying problems, these inconsistencies are not resolved.

Explanation

Mismatches cannot be resolved using the ivdcheck command. The command ivdcheck --fsc-media PartitionName --autocorrect only resolves situations when information is missing either in the File System Catalog or on OA media.

Workaround

To solve this problem, the problematic files need to be re-migrated. Proceed as follows:
1. Put each problematic file on the migration candidate list:
ivdfile --migrate FileName...
2. Trigger migration on the OA partition that stores the problematic files:
ivdfile --trigger-migration PartitionName
For more information on the ivdfile command, see the ivdfile entry in the OA man pages.

Description

Execution of the ivdcheck --fsc-media command seems to complete successfully, however, the following message is written to the OA event log:
ERROR: FAILED creating new FRI... ...No space left on device.

Explanation

The file system that stores the temporary Fast Recovery Information files ran out of free space.
Fast Recovery Information is located in the directory /var/opt/ivd/fri.

Workaround

Extend the size of the volume that stores the file system for Fast Recovery Information and run the consistency check again. The formula for the estimated maximum size for the temporary Fast Recovery Information files is given in the OA Installation Guide for a particular platform. For space requirements of the ivdcheck --fsc-media command, you have to consider the total number of full and open medium volumes (instead of the number of open medium volumes) to calculate the nv variable.

Description

During the execution of an OA deletion job, warnings are not logged in the OA event log file for non-existing paths.

Explanation

Paths specified in the Path variable in the deletion-policy part of an OA partition configuration file are not checked to see if they exist during execution of the corresponding OA deletion jobs on this partition.

Workaround

None

Description

After an OA partition is removed from the OA configuration, the partition-specific files are not deleted.

(External OA client specific)

Explanation

The HSMDB, located on the external OA client, is not removed during removal of the OA partition.

Workaround

After removing the OA partition from the OA configuration, manually delete the corresponding directory and its contents from the external OA client.
On Linux OA clients, delete the directory /var/opt/ivd/part/PartitionName.

Description

The following error message is displayed in the OA error log:
[2005/03/02 10:39:56, ivd_host, 002680, PMG, <PartitionName>, 0, ] CRITICAL ERROR:
File:
fsc_nsDirEntry.lrf vector at index 6042669 of size 4 was released twice.
A DB recovery needs to be done in near future. Pack DB and contact support for further steps.

Explanation

n/a

Workaround

Recover the File System Catalog (FSC) of the OA partition PartitionName. For details, see ”File System Catalog recovery” on page 309.

Description

The following error message is displayed in the OA error log:
[2005/03/02 10:39:56, ivd_host, 002680, PMG, <PartitionName>,, 0, ] CRITICAL ERROR:
File:
hsmDirEntry.lrf vector at index 6042669 of size 4 was released twice.
A DB recovery needs to be done in near future. Pack DB and contact support for further steps.

Explanation

n/a

Workaround

Recover the Hierarchical Storage Management Database (HSMDB) of the OA partition PartitionName by performing the following steps:
1. Unmount the belonging HSM file system.
2. Delete the HSMDB directory from the local system.

Path of the HSMDB directory is /var/opt/ivd/part/PartitionName/hsm.

Description

When trying to configure a new OA resource using the --add option in the OA command-line interface, the command fails and reports the following error message:
ERROR: 3000: Parser error. 'Undefined member function Assign(str, str). at line number:0'

Explanation

You may have used a hyphen character (-) as part of a variable value in the configuration file for the OA resource, and removed the surrounding double quote characters (").

Workaround

Enclose the value of the problematic variable in double quotes (") and retry adding the OA resource.