Bug 763371 (GLUSTER-1639) - gnfs must check for existing nfs servers and report error
Summary: gnfs must check for existing nfs servers and report error
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-1639
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.1-alpha
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-18 10:18 UTC by Shehjar Tikoo
Modified: 2011-04-26 06:12 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description Shehjar Tikoo 2010-09-18 10:18:23 UTC
Many people are running into scenarios where knfs or another glusterfs server is already running and:

a. exports from the new server dont show up in showmount

or

b. the exports show up but mount requests fail because the client sends the mount request to the old nfs servers, failing the requests.


The trick is to perform getport requests to check whether the portmapper already has a registration for nfs and associated protocols.

Comment 1 Amar Tumballi 2011-04-25 09:33:27 UTC
Please update the status of this bug as its been more than 6months since its filed (bug id < 2000)

Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.

Comment 2 Shehjar Tikoo 2011-04-26 03:12:14 UTC
Closing. nobody is complaining without this feature.


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