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

Table 1-3
Veritas File System fixed issues (continued)
DescriptionIncident
Fixed the cause of a panic in the volkio_to_kio_copy()
call.
1665456
Fixed an incorrect alert generation from VxFS when the file
system usage threshold is set.
1805046
Fixed the cause of a system panic in inctext, in which
VTEXT was not set and tcount was greater than 0.
1828175
Fixed an issue in which a panic could happen because of a
mutex getting destroyed while the protected structure was
still in use.
1903977
You can now mount deprecated disk layout versions so that
they can be upgraded.
1922948
Direct I/O can now be enabled using the mincache and
convosync mount options with the base VxFS license.
1926141
Storage Checkpoint creation now properly fails to assign a
metadata allocation policy on a data-only volume.
1935374
Setting vxfs_bc_bufhwm higher than the available physical
memory now reports an error.
1945171
Fixed a performance issue in fsadm where fsadm kept
relocating and copying already reorganized regions of a file
in subsequent passes.
1946063
Interchanged the order in which fcache_vn_destroy()
and VFS_TEARDOWN_STACK() are called to avoid a panic.
1969314
The virtual memory area is no longer destroyed if there are
active mappings on the vnode Fix to during a force unmount.
2017776
The fsppadm command no longer dumps core if a volume
does not have placement tags.
2018439
Added quota support for the user "nobody".2026603
The sar -v command now properly reports VxFS inode
table overflows.
2026625
Fixed the cause of ENOTBLK being returned via the async
driver due to fdd not being a block device.
2026675
23Storage Foundation Cluster File System Release Notes
Fixed issues