Bug 763784 (GLUSTER-2052) - [glusterfs 3.1.1qa4]: ping-pong data-increment values go berserk
Summary: [glusterfs 3.1.1qa4]: ping-pong data-increment values go berserk
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-2052
Product: GlusterFS
Classification: Community
Component: locks
Version: 3.1-beta
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 12:16 UTC by Rahul C S
Modified: 2013-12-09 01:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Rahul C S 2010-11-03 12:16:39 UTC 
Steps:
1. Created a distribute volume having 2 bricks with stat-prefetch on.
2. Mounted 2 glusterfs clients and wrote some files.
3. Started ping-pong client from one glusterfs client (/client1). Working fine.
4. Started ping-pong client for the same file from another glusterfs client(/client2), data increment value did not increase to 2.
5. Started one more ping-pong client for the same file from /client1, the data increment values go berserk and start printing values randomly on /client1
6. Started ping-pong client for the same file from /client2, and the same property is seen in /client2.
Comment 1 Rahul C S 2010-11-11 12:06:51 UTC 
Seeing the same issue in distributed-replicate volume when one more lock program is run on the same file.
Comment 2 Alexander Akhobadze 2011-01-13 04:56:45 UTC 
I have the same issue using 
glusterfs-3.1.1.tar 
MD5: 4584710ADEE36920C97A658B25A1446D
SHA1: 4CBDB6381AADC5B8053487FABD2CEDB1BF0AF0CE
on OpenSuSE
uname -a
... 2.6.34.7-0.4-default #1 SMP 2010-10-07 19:07:51 +0200 i686 i686 i386 GNU/Linux
Comment 3 shishir gowda 2011-04-11 03:45:54 UTC 
went through the ping-pong code, and found that it checks for negative values in unsigned variables.

Closing this bug as its invalid.
Note You need to log in before you can comment on or make changes to this bug.