> can any one explain me how does file locking work on isilon

A good and quite recent read for this general question is:

Isilon OneFS fundamentals of locks and locking

It might help you, together with more specific information on the customer's system

that you might be able to collect (and possibly share it here).

Like for example, what locks do the processes actually attempt to acquire

in order to achieve this:

>customer is expecting  first two files locked by server1 while the last one locked by server2

and also, what behavior is then produced -- which locks get established?

Cheers

-- Peter

In addition to what Peter said - I assume we are talking NFSv4 because MQ wants that.    MQ demands NFSv4 advisory locking - OneFS supports that so MQ should work.

Also, what version of OneFS are you running?   OneFS 8.0 improved the NFSv4 lock failover logic so your best chance of success will be with OneFS 8.0.

Cheers,
Chris

Hi Chris,

we are running on NFS v3 not v4

and this is something I got it from IBM website

'Modern file systems, such as NFS v4, use leased locks to detect failures and then release locks following a failure. Older file systems, such as NFS v3 that do not have a reliable mechanism to release locks after a failure, must not be used with multi-instance queue managers.'

the lock is not happening as customer wants, is it because we are not on NFS V4?

If this issue is still outstanding, IBM MBMQ works well with Isilon if NFS export is mounted with same IP address across client instances. This is going against Isilon load-balancing but have to work around it someway.