[Gluster-devel] Gluster Code Metrics Weekly Report

2023-02-02 Thread sheggodu

Gluster Code Metrics


Metrics Values

Clang Scan 64

Coverity 93

Line Cov

Func Cov


Trend Graph

Check the latest run:
Coverity Clang Code Coverage
---

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



[Gluster-devel] [Smallfile-Replica-3] Performance report for Gluster Upstream - 03/02/2023 Test Status: PASS (5.55%)

2023-02-02 Thread Gluster-jenkins


final.csv
Description: Binary data
---

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



[Gluster-devel] Coverity Warning Alert

2023-02-02 Thread sheggodu

Current Threshold: 16. Coverity Warning Latest Count:  93

---

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



Re: [Gluster-devel] Regarding Glusterfs file locking

2023-02-02 Thread Strahil Nikolov
 As far as I remember there are only 2 types of locking in Linux:
- Advisory
- Mandatory

In order to use mandatory locking, you need to pass the "mand" mount option to 
the FUSE client(mount -o mand, ...) and chmod g+s,g-x 
//


Best Regards,
Strahil Nikolov
 В сряда, 1 февруари 2023 г., 13:22:59 ч. Гринуич+2, Maaz Sheikh 
 написа:  
 
  #yiv5808026394 P {margin-top:0;margin-bottom:0;}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-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 SheikhAssociate 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

  ---

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