17.08.2015 Views

Veritas Storage Foundation Release Notes

Veritas Storage Foundation™ Release Notes: HP-UX - Symantec

Veritas Storage Foundation™ Release Notes: HP-UX - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />

Known issues<br />

51<br />

vxdisksetup fails on a LUN that is larger than 1 TB and has the<br />

cdsdisk format if the system is using Tachyon HBAs (2146340)<br />

The vxdisksetup command fails to initialize a LUN that is larger than 1 TB and<br />

has the cdsdisk format if the system is using Tachyon HBAs. The vxdisksetup<br />

command displays the following error:<br />

VxVM vxdisk ERROR V-5-1-5433 Device disk_name: init failed:<br />

Work-around:<br />

Disk is not useable, bad format<br />

There is no workaround for this issue.<br />

Shared disk group creation on slave fails if the naming scheme<br />

on slave is operating system native scheme with the mode as<br />

the new name (2148981)<br />

While creating shared disk groups on slaves using the command's shipping feature,<br />

the disk group creation may fail if the naming scheme on the slave where the<br />

command was issued is the operating system's native scheme with the mode as<br />

the new name.<br />

Workaround:<br />

You can create the shared disk group from the slave by changing the naming<br />

scheme to the operating system's native scheme while in the "Legacy" mode.<br />

vxdisk -f init can overwrite some of the public region contents<br />

(1190117)<br />

If a disk was initialized by a previous VxVM version or defined with a smaller<br />

private region than the new default of 32 MB, then the public region data will be<br />

overridden.<br />

Workaround:<br />

Specify explicitly the length of privoffset, puboffset, publen, and privlen while<br />

initializing the disk.<br />

vxsnap addmir command sometimes fails under heavy I/O load<br />

(2441283)<br />

The vxsnap addmir command sometimes fails under heavy I/O load and produces<br />

multiple errors.<br />

Workaround: Rerun the vxsnap addmir command.

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

Saved successfully!

Ooh no, something went wrong!