vnx gate way 8

Praveen_td,

It is controlled by the following data mover parameter (default is cooperative and note that data mover reboot is required):

parameter nfsv4.advisoryLocking

server_param server_2 -facility nfsv4 -info advisoryLocking -verbose

server_2 :

name                    = advisoryLocking

facility_name           = nfsv4

default_value           = 0

current_value           = 0

configured_value        =

user_action             = reboot DataMover

change_effective        = reboot DataMover

range                   = (0,1)

description             = When 1, sets file locking mode to advisory (like NFSv3); Default is 0 for mandatory locking (like CIFS).

detailed_description

Sets file locking mode to advisory if 1. Advisory locking is compatible with NFSv3: Applications using file locks must be cooperative: A file lock doesn't prevent conflicting I/Os. Default is mandatory locking (like CIFS).

For more information, you can also reference the "Configuring NFS on VNX" document on support.emc.com.

Do you use a particular application that needs advisory and not mandatory locking ?

Oops, yeah default is mandatory.  Thanks for the correction.

Hi ALL,

I have below questions...

1)How to use advisory locking for a particular application?

2-a) If we enable nfsv4 and if we change from mandatory locking to advisory locking then all the shares will be have advisory locking?

2-b) If all the shares have advisory locking then, if for particular share need mandatory locking what is the case? How to make this happen?

Thanks,

Praveen

Hi,

Yes we do have a particular application for advisory locking...

Which application is it ?

So far I have only heard about one specific IBM application that wanted advisory locking or it wouldn’t work after an application failover

We are going to use it for IQ Series....

We have seen this required by IBM WebSeries MQ 7

yes we need this for MQ series and we have changed the parameter for advisory locking and the output is below.

server_param server_2 -facility nfsv4 -info advisoryLocking -verbose

server_2 :

name                    = advisoryLocking

facility_name           = nfsv4

default_value           = 0

current_value           = 1

configured_value        = 1

user_action             = reboot DataMover

change_effective        = reboot DataMover

range                   = (0,1)

description             = When 1, sets file locking mode to advisory (like NFSv3); Default is 0 for mandatory locking (like CIFS).

detailed_description

Sets file locking mode to advisory if 1. Advisory locking is compatible with NFSv3: Applications using file locks must be cooperative: A file lock doesn't prevent conflicting I/Os. Default is mandatory locking (like CIFS).

===========================================================================

Can somebody tell me the command to export the file system with nfsv4.

Also since advisory locking is enabled for this nfsv4 do we need to specify seperately any param for advisory locking or it will automatically take be advisory locking.

Many Thanks,

Praveen

Hi,

just a regular server_export

see the Configuring NFS on VNX manual on how to enable NFSv4 and other setup work needed.

Once that param is enabled you’ll get advisory locking with NFSv4 for all NFS exports on that data mover

Hi ALL,

We have enabled nfsv4 and advisory locking in VG8.

Below are the steps we have exported a file system.

a)create the interface and route.

b)create a vdm.

c)create a file system and mount the fs on vdm with Mixed policy.

d)export the fs via PDM (server_2) with nfsv4 option.

Now the issue is with performance of this export is very poor. Export is mounted on the host end and it is giving very poor performance.

Note: In the same existing environment nfsv3 share is there and the performance is good for this.

we have tried with nfsv4 delegation option with None and RW.

Please suggest us any other steps to follow to increase the performance for this nfsv4 export.

Thanks,

Praveen