VFS_GPFS(8) System Administration tools VFS_GPFS(8)NAME
vfs_gpfs - gpfs specific samba extensions like acls and prealloc
SYNOPSIS
vfs objects = gpfs
DESCRIPTION
This VFS module is part of the samba(7) suite.
The gpfs VFS module is the home for all gpfs extensions that Samba requires for proper integration with GPFS. It uses the GPL library
interfaces provided by GPFS.
Currently the gpfs vfs module provides extensions in following areas :
o NFSv4 ACL Interfaces with configurable options for GPFS
o Kernel oplock support on GPFS
o Lease support on GPFS
NOTE:This module follows the posix-acl behaviour and hence allows permission stealing via chown. Samba might allow at a later point in
time, to restrict the chown via this module as such restrictions are the responsibility of the underlying filesystem than of Samba.
This module is stackable.
OPTIONS
nfs4:mode = [ simple | special ]
Enable/Disable substitution of special IDs on GPFS. This parameter should not affect the windows users in anyway. It only ensures that
Samba sets the special IDs - OWNER@ and GROUP@ ( mappings to simple uids ) that are relevant to GPFS.
The following MODEs are understood by the module:
o simple(default) - do not use special IDs in GPFS ACEs
o special - use special IDs in GPFS ACEs.
nfs4:acedup = [dontcare|reject|ignore|merge]
This parameter configures how Samba handles duplicate ACEs encountered in GPFS ACLs. GPFS allows/creates duplicate ACE for different
bits for same ID.
Following is the behaviour of Samba for different values :
o dontcare (default) - copy the ACEs as they come
o reject - stop operation and exit with error on ACL set op
o ignore - don't include the second matching ACE
o merge - bitwise OR the 2 ace.flag fields and 2 ace.mask fields of the 2 duplicate ACEs into 1 ACE
nfs4:chown = [yes|no]
This parameter allows enabling or disabling the chown supported by the underlying filesystem. This parameter should be enabled with
care as it might leave your system insecure.
Some filesystems allow chown as a) giving b) stealing. It is the latter that is considered a risk.
Following is the behaviour of Samba for different values :
o yes - Enable chown if as supported by the under filesystem
o no (default) - Disable chown
EXAMPLES
A GPFS mount can be exported via Samba as follows :
[samba_gpfs_share]
vfs objects = gpfs
path = /test/gpfs_mount
nfs4: mode = special
nfs4: acedup = merge
CAVEATS
The gpfs gpl libraries are required by gpfs VFS module during both compilation and runtime. Also this VFS module is tested to work on SLES
9/10 and RHEL 4.4
VERSION
This man page is correct for version 3.0.25 of the Samba suite.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
The GPFS VFS module was created with contributions from Volker Lendecke and the developers at IBM.
This manpage was created by the IBM FSCC team
Samba 3.5 06/18/2010 VFS_GPFS(8)
Check Out this Related Man Page
VFS_SHADOW_COPY2(8) System Administration tools VFS_SHADOW_COPY2(8)NAME
vfs_shadow_copy2 - Expose snapshots to Windows clients as shadow copies.
SYNOPSIS
vfs objects = shadow_copy2
DESCRIPTION
This VFS module is part of the samba(7) suite.
The vfs_shadow_copy2 VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows
Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares.
This is a 2nd implementation of a shadow copy module. This version has the following features:
1. You don't need to populate your shares with symlinks to the snapshots. This can be very important when you have thousands of shares, or
use [homes].
2. The inode number of the files is altered so it is different from the original. This allows the 'restore' button to work without a
sharing violation.
This module is stackable.
CONFIGURATION
vfs_shadow_copy2 relies on a filesystem snapshot implementation. Many common filesystems have native support for this.
Filesystem snapshots must be mounted on specially named directories in order to be recognized by vfs_shadow_copy2. The snapshot mount
points must be immediate children of a the directory being shared.
The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where:
o YYYY is the 4 digit year
o MM is the 2 digit month
o DD is the 2 digit day
o hh is the 2 digit hour
o mm is the 2 digit minute
o ss is the 2 digit second.
The vfs_shadow_copy2 snapshot naming convention can be produced with the following date(1) command:
TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
OPTIONS
shadow:snapdir = SNAPDIR
Path to the directory where snapshots are kept.
shadow:basedir = BASEDIR
Path to the base directory that snapshots are from.
shadow:fixinodes = yes/no
If you enable shadow:fixinodes then this module will modify the apparent inode number of files in the snapshot directories using a hash
of the files path. This is needed for snapshot systems where the snapshots have the same device:inode number as the original files
(such as happens with GPFS snapshots). If you don't set this option then the 'restore' button in the shadow copy UI will fail with a
sharing violation.
EXAMPLES
Add shadow copy support to user home directories:
[homes]
vfs objects = shadow_copy2
shadow:snapdir = /data/snaphots
shadow:basedir = /data/home
CAVEATS
This is not a backup, archival, or version control solution.
With Samba or Windows servers, vfs_shadow_copy2 is designed to be an end-user tool only. It does not replace or enhance your backup and
archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a version control
system.
VERSION
This man page is correct for version 3.2.7 of the Samba suite.
AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open
Source project similar to the way the Linux kernel is developed.
Samba 3.5 06/18/2010 VFS_SHADOW_COPY2(8)