HP-UX Virtual Partitions Release Notes (A.05.01)

Known Problems and Workarounds
Deletion of float memory fails with asyncdsk driver
Chapter 3 27
Deletion of float memory fails with asyncdsk driver
Related JAG or Patch ID Number
JAGag03862
Applicable on
❏ vPars A.05.01
Description
Many applications, such as databases, use the asyncdsk driver to lock down
memory for I/O transfers. As of this writing, the asyncdsk driver does not
support memory deletion. As a result, if the asyncdsk driver has locked
down any float memory, then that portion of memory cannot be deleted from
a virtual partition.
Symptoms
If the deletion failed because the memory was locked down, the
/var/adm/syslog/syslog.log file on the target partition will contain the
error code “252(ENOTSUP)”.
Workaround
There are several workarounds available. You can either
• Halt the database application(s). Delete the float memory and then
restart the database application(s).
or
• Most database applications lock down memory at startup and do not
reconfigure locked memory after that. For such database applications,
boot the virtual partition with base memory only. After starting the
application(s), add the float memory to the virtual partition. This
enables deletion of this float memory later.
or
• When available, install a patch to the asyncdsk driver. This patch
implements the callback mechanism to allow deletion of memory that
was locked down by the asyncdsk driver. For updates on patch