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

m
mount_vxfs(1M) mount_vxfs(1M)
policy is in effect.
Behavior on cluster file systems is somewhat different. If the policy selected is
disable,
the file system is disabled only on the node where the I/O error occurs. The file system is
still accessible from the other nodes. If the I/O error is on the CFS primary, a new primary
is elected from the remaining nodes and the original primary becomes a secondary.
disable is the recommended policy for cluster file systems. With any other policy, a
metadata I/O error can mark the file system for a full file system check. If the CFS primary
subsequently fails, the other nodes in the cluster cannot take over the primaryship, thereby
disabling access to the file system from all nodes in the cluster.
Note: If the CVM disk detach policy (the way unusable disks in a shared disk group are
detached) is
local, the I/O error policy must be
disable.
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 ena-
bling 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. The performance of some storage devices (specifically, devices using the read-
modify-write feature) improves if the writes are issued in one or more multiples of a
particular size. When a file system is mounted with the logiosize option, VxFS writes
the intent log in at least size bytes, or a multiple of size bytes, to obtain the maximum per-
formance from such devices. The values for size can be 1024, 2048, or 4096.
log|delaylog|tmplog|nolog
Control intent logging. To maintain file system integrity after a system failure, logging
must be enabled. In log 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. The default
is delaylog. 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 performance, 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 VX_DSYNC caching advisory
was set.
The
unbuffered 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_UNBUFFERED caching advisory was set.
Section 1M−−478 Hewlett-Packard Company − 5 − HP-UX 11i Version 2: September 2004