Veritas File System 5.0 Release Notes, HP-UX 11i v3, First Edition, May 2008

• Problem
The write(2) system call does not modify the m_time of a FIFO after some operations
are completed on the FIFO.
This issue occurs when the owner of the FIFO is different from the process who is writing
to it and the writer process has the write permission on the FIFO. When the owner and
writer process are the same, or when a root process is writing the FIFO, the m_time is
modified appropriately. Also, this problem occurs only with FIFOs. This error does not occur
with regular files.
Workaround
No workaround exists for this problem.
• Problem
After a Transfer of Control (TOC) of the system, multiple device special files are found for
the same physical disks.
Workaround
HP recommends against performing a TOC of any system, because a TOC does not allow
the operating system to properly shut down, triggering the possibility of problems like this
one. Unexpected power failures might also trigger this problem and can be avoided with
uninterrupted power supplies and other similar data center technology.
• Problem
File systems with quotas cannot be mounted after cross-platform data sharing conversion.
If a file system is using quotas, it cannot be mounted with quotas turned on after converting
the byte order of the file system with the fscdsconv utility. Similarly, quotas cannot be
turned on if the converted file system is first mounted with quotas turned off.
Workaround
No workaround exists for this problem.
• Problem
The VxFS utility fsck may terminate when applied to unclean file systems of VxFS 4.0 or
4.1. Due to an incompatibility between the VxFS 5.0 and 4.0, and 4.1 releases, the fsckutility
may terminate during intent log replay if run on older file systems. This only affects file
systems that were previously running under VxFS 4.0 or 4.1 that are CVM-shared volumes
or multi-volume file systems, and that were not cleanly unmounted prior to use in VxFS
5.0.
Workaround
Perform a full fsck to bring the file system to a consistent, clean state that is ready to be
mounted. For more information, see fsck_vxfs(1M).
• Problem
If you modify the value for the fcl_keeptime parameter using the vxtunefs command,
you cannot reset the value back to the default value of 0.
Workaround
No workaround exists for this problem.
• Problem
Calling the mmap (2) function on a large offset of a file requires a large amount of swap
space. If mmap (2) is called on a 1 TB offset in MAP_SHARED mode, then approximately 256
MB of virtual memory pages can be instantiated. This means that the Virtual Memory
subsystem requires space to hold 256 MB of data structures. Each of these structures are 16
bytes, thus approximately 4 GB space is required. Since these data structures page out, more
than 4 GB of swap space is reserved when mmap (2) is called.
Known Problems And Workarounds 17