Bug 917459 - gnfs+quota: ping_pong does not work properly with quota disable
Summary: gnfs+quota: ping_pong does not work properly with quota disable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: vpshastry
QA Contact: Saurabh
URL:
Whiteboard:
Depends On:
Blocks: 956494 969461 1652103 1652119 1652123 1652126 1652156 1652314 1652315 1652317
TreeView+ depends on / blocked
 
Reported: 2013-03-04 05:23 UTC by Saurabh
Modified: 2019-07-05 15:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:39:27 UTC
Embargoed:

Attachments (Terms of Use)

Description Saurabh 2013-03-04 05:23:45 UTC 
Description of problem:
vol type  :- 6x2 


Version-Release number of selected component (if applicable):
glusterfs-3.3.0.5rhs-43.el6rhs.x86_64

client,
RHEL 6.4
How reproducible:
saw it first time

Steps to Reproduce:
1. volume 6x2 
2. mount on a client using nfs
3. ping_pong a 5, from two instances of same mount on same client and one more on a different client.
4. enable quota
5. disable quota
6. ctrl+c to stop 3 instances of ping_pong as they are hung.
7. start ping_pong on any of them again
8. vol reset
9. vol restart
  
Actual results:
step 3, works fine.
step 4, works fine.
step 5, the ping pong displays this on all three nodes,

[root@rhsauto036 nfs-test]# /opt/qa/tools/ping_pong a 5
lock at 1 failed! - No locks available
^C     3 locks/sec

though quota gets disabled.

step7, just hangs, no report of locks being held.

ste8, same as step7.

step9, same as step7

though other operations are a Pass.

Expected results:

ping pong should have worked properly after quota disable
ping_pong should not hang.
Additional info:
nfs.log doesn't point out any errors all through the sequence of operations.
Comment 2 Saurabh 2013-03-04 05:39:15 UTC 
[2013-03-03 21:28:00.610560] Volume reset : volume  : dist-rep
[2013-03-03 21:28:00.610661] Volume reset :  on volume dist-rep  SUCCEDED 
[2013-03-03 22:03:59.598368] volume quota :  enable command on dist-rep
[2013-03-03 22:03:59.598472] volume quota :  enable command on dist-rep SUCCEEDED
[2013-03-03 22:08:23.528016] volume quota :  disable command on dist-rep
[2013-03-03 22:08:23.528132] volume quota :  disable command on dist-rep SUCCEEDED
[2013-03-03 22:14:41.644313] Volume reset : volume  : dist-rep
[2013-03-03 22:14:41.644417] Volume reset :  on volume dist-rep  SUCCEDED 
[2013-03-03 22:25:00.276695] Volume stop : on volname: dist-rep SUCCESS
[2013-03-03 22:25:04.810828] volume start : on volname: dist-rep SUCCESS
[root@rhsauto032 ~]#
Comment 5 Scott Haines 2013-09-23 22:39:27 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Comment 6 Scott Haines 2013-09-23 22:43:44 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Note You need to log in before you can comment on or make changes to this bug.