Bug 1428808 - [GANESHA] Ganesha process aborted on the node having VIP from which volume is mounted while performing renaming and lookups from 4 clients
Summary: [GANESHA] Ganesha process aborted on the node having VIP from which volume i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.2
Hardware: All
OS: All
urgent
high
Target Milestone: ---
: RHGS 3.2.0
Assignee: Daniel Gryniewicz
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On: 1428798
Blocks: 1351528
TreeView+ depends on / blocked
 
Reported: 2017-03-03 12:04 UTC by Soumya Koduri
Modified: 2017-03-23 06:29 UTC (History)
13 users (show)

Fixed In Version: nfs-ganesha-2.4.1-8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1428798
Environment:
Last Closed: 2017-03-23 06:29:23 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0493 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.2.0 nfs-ganesha bug fix and enhancement update 2017-03-23 09:19:13 UTC

Comment 2 Soumya Koduri 2017-03-03 12:05:36 UTC 
This bug is to track ABRT issue observed.

Upstream patch link - https://review.gerrithub.io/#/c/308163/
Comment 5 Manisha Saini 2017-03-07 11:38:57 UTC 
Verified this bug on 

nfs-ganesha-gluster-2.4.1-8.el6rhs.x86_64

Steps:

1.Create a 5 node ganesha cluster
2.Create 6*2 Distributed-Replicate volume and Enable ganesha on it.
3.In the export file provide RO permission to 3 clients

# showmount -e localhost
Export list for localhost:
/ganesha 10.70.37.192,10.70.37.176,10.70.37.129

4.Mount volume to 4 clients via v4 with 1 VIP


1st Client- Creating 2000 directories and renaming the same
2nd Client-lookups ls -lRt in loop (having RO permission)
3rd Client -lookups ls -lRt in loop (having RO permission)
4th Client- lookups ls -lRt in loop (having RO permission)

As the issue is no more observed with this build,hence marking this bug as verified.
Comment 7 errata-xmlrpc 2017-03-23 06:29:23 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.

https://rhn.redhat.com/errata/RHEA-2017-0493.html
Note You need to log in before you can comment on or make changes to this bug.