Veritas Storage Foundation 5.1 SP1 Cluster File System Release Notes (5900-1509, April 2011)

Panic due to null pointer de-reference in vx_unlockmap()
(2059611)
A null pointer dereference in the vx_unlockmap() call can cause a panic. A fix for
this issue will be released in a future patch.
Workaround: There is no workaround for this issue.
Veritas Volume Manager known issues
The following are the Veritas Volume Manager known issues for this release.
vxdg split or join operations can fail for disks with a disk media
name greater than or equal to 27 characters (2063387)
If a disk's media name is greater than or equal to 27 characters, certain operations,
such as diskgroup split or join, can fail with the following error:
VxVM vxdg ERROR : vxdg move/join dg1 dg2 failed subdisk_name : Record
already exists in disk group
VxVM uses disk media names to create subdisk names. If multiple subdisks are
under the same disk, then the serial number, starting from 1, is generated and
appended to the subdisk name so as to identify the given subdisk under the physical
disk. The maximum length of the subdisk name is 31 characters. If the disk media
name is long, then the name is truncated to make room for serial numbers.
Therefore, two diskgroups can end up having same subdisk names due to this
truncation logic, despite having unique disk media names across diskgroups. In
such scenarios, the diskgroup split or join operation fails.
Workaround:
To avoid such problems, Symantec recommends that disk media name length
should be less than 27 characters.
After initializing a disk for native LVM, the first instance of
vxdisk list fails with a 'get_contents' error and errant flags are
displayed (2074640)
After you initialize a disk that is under the operating system's native LVM control
and not under Veritas Volume Manager (VxVM) control by using the pvcreate
path_to_physical_disk command, the first time that you run the vxdisk list
disk_name command results in a VxVM error message related to get_contents,
and the flags field is incorrectly populated. However, in the next instantiation
of the same command, VxVM does not produce an error and the flags are correctly
populated with the LVM tag.
35Storage Foundation Cluster File System Release Notes
Known issues