HP CIFS Server Administrator Guide Version A.02.04.04 (5070-6710, October 2011)

For more information on the template and using CFSM with other stackable file system modules,
see the “Using CFSM with Other Stackable File System Modules” section and the fstadm man
page.
Stacking CFSM Using the mount Command
CFSM can be added to any locally mounted file system (like VxFS or HFS). To add CFSM to a file
system, the file system must first be unmounted, then execute the mount command with the "-o
stackfs=cfsmtemplate" option to stack and mount the file system.
For example, the following command stacks CFSM onto the physical file system using the
cfsmtemplate template, when mounting the physical file system mounted on /mnt:
mount -F vxfs -o stackfs=cfsmtemplate /dev/dsk/c1t2d3 /mnt
Unstacking CFSM Using the umount Command
No special option is needed to unstack CFSM. Use the umount command to unstack and unmount
the physical file system.
For example, the following command unstacks CFSM when unmounting the physical file system
mounted on /mnt:
umount /mnt
Configuring CIFS for CFSM in /etc/fstab
If the system is rebooted, CFSM will no longer be used on that file system. To use a stackable
CFSM on a file system permanently (across reboots), add the "stackfs=cfsmtemplate" option
to the file entry in the /etc/fstab file. This file contains the information about all the currently
mounted file systems.
For example, the following entry in /etc/fstab uses a stackable CFSM on the physical file system
mounted on /mnt:
/dev/dsk/c1t5d6 /mnt vxfs stackfs=cfsmtemplate 0 2
Configuring CIFS for CFSM in smb.conf
To use CFSM, you must configure the following parameters in smb.conf properly: They can be
configured globally or on a per-share basis. The global parameter is set to the default value for
all shares. The share specific parameter setting can override the global default setting for the
individual shares. Refer to the smb.conf man pages for details.
• locking: This boolean variable controls whether locking will be performed by the server in
response to lock requests from the client. You must set this option to yes (the default setting).
• posix locking: The SMBD daemon maintains the database of CIFS file locks obtained by
SMB clients. posix locking is a boolean variable that controls whether the CIFS Server
maps the CIFS file locks to POSIX locks. You must Set this option to yes (the default setting).
• share modes: This boolean parameter controls whether to enable or disable the honoring
of the share modes during a file open. These modes are used by clients to gain exclusive read
or write access to a file. You must set this option to yes (the default setting).
• kernel oplocks: It is a boolean variable. If set it to yes, HP-UX processes and NFS clients
can concurrently access files with CIFS clients with no risk of file corruption when opportunistic
locking is turned on. You must set it to yes if oplocks is turned on. Both kernel oplocks
and oplocks are turned on by default.
If the above parameters are not configured properly with CFSM, the concurrent file accesses from
NFS or other local programs may cause file corruption.
You should configure CFSM for file systems where files may be concurrently accessed by CIFS
clients and NFS clients or local processes.
Stacking CFSM 137