HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

m
mount_vxfs(1M) mount_vxfs(1M)
The unbuffered value handles any reads or writes with the
O_SYNC or
O_DSYNC flag as if the VX_UNBUFFERED
caching advisory is set.
The
closesync value delays O_SYNC or O_DSYNC writes so that they do not
take effect immediately.
The
closesync, dsync, direct, and
unbuffered values all run the
equivalent of an fsync(2) to be run when any file accessed with the
O_SYNC or
O_DSYNC flag is closed.
The delay value delays O_SYNC or O_DSYNC
writes so that they do not take
effect immediately. With this option, VxFS changes
O_SYNC or O_DSYNC writes
into delayed writes. No special action is performed when closing a file. This option
effectively cancels data integrity guarantees normally provided by opening a file
with
O_SYNC or O_DSYNC.
NOTE: The convosync option is available only with the HP OnLineJFS product.
datainlog|nodatainlog
Generally, VxFS does O_SYNC
or O_DSYNC writes by logging the data and the
time change to the inode (
datainlog). If the nodatainlog option is used, the
logging of synchronous writes is disabled; O_SYNC writes the data into the file and
updates the inode synchronously before returning to the user.
NOTE: The datainlog option is available only with the HP OnLineJFS product.
largefiles |nolargefiles
These options do not turn largefiles capability on and off (use mkfs_vxfs or
fsadm_vxfs to set and clear the largefiles flag), but they do verify whether a file
system is largefiles capable. If nolargefiles is specified and the mount
succeeds, then the file system does not contain any files whose size is two gigabytes
or larger, and such files cannot be created. If largefiles is specified and the
mount succeeds, then the file system may contain files whose size is two gigabytes
or larger, and large files can be created. For a mount to succeed, the option must
match the largefiles flag as specified by mkfs_vxfs or fsadm_vxfs .
NOTE: Large files are supported on HP-UX 10.20 systems and above. Be careful
when enabling large file system capability. System administration utilities such as
backup may experience problems if they are not large-file aware.
logiosize=1024|2048|4096
Control size of intent log I/O buffers. Default value is determined dynamically at
mount time.
log|delaylog|tmplog|nolog
Control intent logging. To maintain file system integrity after a system failure, log-
ging must be enabled. The default is log.Inlog mode, file system structural
changes are logged to disk before the system call returns to the application. If the
system crashes, fsck_vxfs(1M) completes logged operations that did not complete.
In delaylog mode, some system calls return before the intent log is written.
This improves the performance of the system, but some changes are not guaranteed
until a short time later when the intent log is written. This mode approximates
traditional UNIX system guarantees for correctness in case of system failures.
In tmplog mode, the intent log is almost always delayed. This improves perfor-
mance, but recent changes may disappear if the system crashes. This mode is only
recommended for temporary file systems.
nolog is an alias for tmplog.
mincache=direct|dsync|unbuffered|closesync|tmpcache
Alter the caching behavior of the file system.
The direct value handles any reads without the O_SYNC flag, or any writes
without the O_SYNC flag, VX_DSYNC, VX_DIRECT, and VX_UNBUFFERED
caching advisories, as if the VX_DIRECT caching advisory was set.
The dsync value handles any writes without the O_SYNC flag or one of the
VX_DIRECT, VX_DSYNC,orVX_UNBUFFERED caching advisories as if the
Section 1M−−522 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005