Bug 1310856 - implement BIND_CONN_TO_SESSION
Summary: implement BIND_CONN_TO_SESSION
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: nfs-ganesha
Classification: Retired
Component: MainNFSD
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Frank Filz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 20:00 UTC by Kaleb KEITHLEY
Modified: 2019-11-22 16:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-22 16:00:27 UTC

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

Description Kaleb KEITHLEY 2016-02-22 20:00:51 UTC 
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 20:12:10 UTC 
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.
Comment 2 Kaleb KEITHLEY 2019-11-22 16:00:27 UTC 
looks like BIND_CONN_TO_SESSION is implemented now
Note You need to log in before you can comment on or make changes to this bug.