Bug 1310856 - implement BIND_CONN_TO_SESSION
implement BIND_CONN_TO_SESSION
Status: NEW
Product: nfs-ganesha
Classification: Community
Component: MainNFSD (Show other bugs)
2.4
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Frank Filz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-22 15:00 EST by Kaleb KEITHLEY
Modified: 2016-02-22 15:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kaleb KEITHLEY 2016-02-22 15:00:51 EST
Description of problem:

ESXi clients, e.g., try to use BIND_CONN_TO_SESSION.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Kaleb KEITHLEY 2016-02-22 15:12:10 EST
ESXi clients, e.g., try to use BIND_CONN_TO_SESSION.

If I understood correctly, user mounted from box1 (in a three box cluster).  Then killed box2.  With the gluster HA setup that resulted in two things happening. 1) box2's floating IP moved (to box3?), and 2) box1 and box3's ganesha.nfsd entered NFS-GRACE.  When box1 emerged from grace the ESXi clients' mounts were borked.

A similar setup with Linux clients "survived" the ganesha.nfsd emerging from NFS-GRACE.

It's not clear whether ESXi clients depend on BIND_CONN_TO_SESSION.

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