[Gluster-devel] Coverity Warning Alert

[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] unsubscribe

[Joe Julian]

Hah, sorry about that. The link in the header suggests that should have 
worked.


On 2/3/23 3:38 PM, Joe Julian wrote:



On 2/3/23 3:08 PM, Gluster-jenkins wrote:

Test details:
RPM Location: Upstream
OS Version: Red-Hat-Enterprise-Linux 8.4-(Ootpa)
Baseline Gluster version: glusterfs-10.1-1.
Current Gluster version: glusterfs-20221209.34ce46c-0.0
Intermediate Gluster version: No intermediate baseline
Test type: Largefile
Tool: fio
Volume type: Replica-3
Volume Option: Shard

===
FOPs BaselineDailyBuild  
Baseline vs DailyBuild
===
random-write 17461803 3
random-read  27792784 0
sequential-read  72497231 0
sequential-write 23512353 0
===

---

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
---

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] unsubscribe

[Joe Julian]

On 2/3/23 3:08 PM, Gluster-jenkins wrote:

Test details:
RPM Location: Upstream
OS Version: Red-Hat-Enterprise-Linux 8.4-(Ootpa)
Baseline Gluster version: glusterfs-10.1-1.
Current Gluster version: glusterfs-20221209.34ce46c-0.0
Intermediate Gluster version: No intermediate baseline
Test type: Largefile
Tool: fio
Volume type: Replica-3
Volume Option: Shard

===
FOPs BaselineDailyBuild  
Baseline vs DailyBuild
===
random-write 17461803 3
random-read  27792784 0
sequential-read  72497231 0
sequential-write 23512353 0
===

---

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

[Gluster-devel] [Largefile-Replica-3 with Shard] Performance report for Gluster Upstream - 04/02/2023 Test Status: PASS (0.75%)

[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] [Largefile-Disperse] Performance report for Gluster Upstream - 04/02/2023 Test Status: PASS (2.00%)

[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] [Largefile-Replica-3] Performance report for Gluster Upstream - 04/02/2023 Test Status: PASS (3.25%)

[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] [Smallfile-Disperse] Performance report for Gluster Upstream - 04/02/2023 Test Status: PASS (12.18%)

[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] [Smallfile-Replica-3] Performance report for Gluster Upstream - 04/02/2023 Test Status: PASS (5.55%)

[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

Re: [Gluster-devel] Regarding Glusterfs file locking

[Maaz Sheikh]

Hi,
Greetings of the day,


We checked in GlusterFS documentation for two way replication on three storage 
devices(nodes). Please provide any solution for this. We did not find any 
straight forward information for this scenario.



As per documentation three storage devices(nodes) will work on three way 
replication which does not match our scaling requirement.


Any help is highly appreciated.

Thanks,
Maaz Sheikh

From: Strahil Nikolov 
Sent: Friday, February 3, 2023 4:15 AM
To: gluster-devel@gluster.org ; 
gluster-us...@gluster.org ; Maaz Sheikh 

Cc: Rahul Kumar Sharma ; Sweta Dwivedi 
; Pushpendra Garg 
Subject: Re: [Gluster-devel] Regarding Glusterfs file locking

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.


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 
 написа:


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 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









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