We'll need more specific details on your scenario. For example, are you using SMB and mandatory locking semantics? NFS and advisory locking? If NFS, how are you locking the file? Are you writing with SMB, then reading with NFS? Are you writing to one node, then reading from another node? etc, etc.
In addition to posting here, I would also suggest opening an Isilon Support ticket for things like this...
There is no direct lock interaction between these protocols, but you should be able to utilize filesystem ACLs to prevent user B from manipulating the file being FTP'd by user A (e.g. with a DENY ACE). So I would suggest starting there (unless someone else on the forum can offer more detailed advice)...
kipcranford
125 Posts
0
February 27th, 2015 07:00
We'll need more specific details on your scenario. For example, are you using SMB and mandatory locking semantics? NFS and advisory locking? If NFS, how are you locking the file? Are you writing with SMB, then reading with NFS? Are you writing to one node, then reading from another node? etc, etc.
In addition to posting here, I would also suggest opening an Isilon Support ticket for things like this...
--kip
valic1
2 Posts
0
February 27th, 2015 07:00
I am writing with FTP and reading with SMB
kipcranford
125 Posts
1
February 27th, 2015 09:00
There is no direct lock interaction between these protocols, but you should be able to utilize filesystem ACLs to prevent user B from manipulating the file being FTP'd by user A (e.g. with a DENY ACE). So I would suggest starting there (unless someone else on the forum can offer more detailed advice)...