Team, please let us know if u have any feedback.
________________________________
From: Maaz Sheikh
Sent: Wednesday, January 25, 2023 4:51 PM
To: gluster-devel@gluster.org <gluster-devel@gluster.org>; 
gluster-us...@gluster.org <gluster-us...@gluster.org>
Subject: Regarding Glusterfs file locking

Hi,
Greetings of the day,

Our configuration is like:
We have installed both glusterFS server and GlusterFS client on node1 as well 
as node2. We have mounted node1 volume to both nodes.

Our use case is :
>From glusterFS node 1, we have to take an exclusive lock and open a file 
>(which is a shared file between both the nodes) and we should write/read in 
>that file.
>From glusterFS node 2, we should not be able to read/write that file.

Now the problem we are facing is:
>From node1, we are able to take an exclusive lock and the program has started 
>writing in that shared file.
>From node2, we are able to read and write on that file which should not happen 
>because node1 has already acquired the lock on that file.

Therefore, requesting you to please provide us a solution asap.

Thanks,
Maaz Sheikh
Associate Software Engineer
Impetus Technologies India

________________________________






NOTE: This message may contain information that is confidential, proprietary, 
privileged or otherwise protected by law. The message is intended solely for 
the named addressee. If received in error, please destroy and notify the 
sender. Any use of this email is prohibited when received in error. Impetus 
does not represent, warrant and/or guarantee, that the integrity of this 
communication has been maintained nor that the communication is free of errors, 
virus, interception or interference.
-------

Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk

Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

Reply via email to