HP-UX Reference (11i v2 03/08) - 5 Miscellaneous Topics, 7 Device (Special) Files, 9 General Information, Index (vol 9)

f
fs_async(5) fs_async(5)
(Tunable Kernel Parameters)
If fs_async is set to allow asynchronous writes and a crash occurs,
fsck does not know what sequence
was used, and thus will probably require interactive assistance from the administrator while fixing incon-
sistent file system information, repairing directory and inode entries, and so on.
Why Allow Asynchronous Writes?
Waiting for synchronous writing and updating of disk blocks when closing files after writing to them
degrades the performance of programs and applications that require frequent file and directory write and
close operations. Allowing asynchronous writing significantly reduces those delays, producing a
corresponding improvement in performance. However, when applications are CPU intensive with rela-
tively little disk I/O, performance improvements are much lower.
When Should I Use Asynchronous Writes?
Asynchronous writing is advisable for improving system performance if:
• Risk of power failure is low (very dependable power source and/or uninterruptible power
sources).
• Precautions have been taken to enhance data security (sophisticated file system backup or
redundancy strategies), or potential loss of data due to a system crash is less important than sys-
tem performance.
• User applications require frequent opening, writing, and closing of disk files and directories.
• Elimination of synchronous writing would improve system performance sufficiently to offset any
associated risks.
To enable asynchronous writing, set the
fs_async kernel parameter to 1 instead of the default value of
0.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its
meaning changed in future releases of HP-UX.
AUTHOR
fs_async was developed by HP.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2) fsck(1M), open(2).
HP-UX 11i Version 2: August 2003 − 2 − Hewlett-Packard Company Section 5−−99