To Next Page

To Previous Page

server_mount

401

The server Commands

[renamepolicy={CIFS | FULL | NO}]

Enables or disables control if any file or directory is opened on the

current directory or any subdirectory, before the current directory

is renamed. CIFS (default) stops the renaming of CIFS directories

when in use by CIFS clients. FULL denies permission for the

renaming of CIFS and NFS directories when in use by CIFS or

NFS clients. NO automatically performs the directory rename

without checking if a CIFS or NFS client is opening the directory.

Note: The renamepolicy is not supported by NFSv4.

cifsnanoroundup

Rounds up to the next second any date set by a CIFS client.

For NFS Clients Only: [nolock | wlock | rwlock]

Indicates the impact of locking behavior on NFSv2 and NFSv3

clients against NFSv4 and CIFS file locking. In NFSv2 and NFSv3,

locking rules are cooperative, so a client is not prevented from

accessing a file locked by another client if it does not use the lock

procedure. NFSv2 and NFSv3 locks as advisory. An advisory lock

does not affect read and write access to the file, but informs other

users that the file is already in use

Note: NFSv4 and ClFS clients have mandatory locking schemes and

don't require a locking policy. .

nfsv4delegation={NONE | READ | RW}

Indicates that specific actions on a file are delegated to the NFSv4

client. NONE indicates that no file delegation is granted. READ

indicates only read delegation is granted. RW (default) indicates

write delegation is granted.

SEE ALSO Managing Celerra Volumes and File Systems with Automatic Volume

Management, Managing Celerra Volumes and File Systems Manually,

Locking Policy NFS clients can:

nolock (default) can open and write to a file when it is locked by CIFS or NFSv4

clients.

wlock can read but cannot write data to a file locked by CIFS or NFSv4 clients.

rwlock (recommended) can’t read or write data to files locked by CIFS or NFSv4

clients.

EMC Celerra User Manual

Other manuals for EMC Celerra