Bug 764427 (GLUSTER-2695) - Mac host showmount -a not working.
Summary: Mac host showmount -a not working.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2695
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.1.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Gaurav
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 10:58 UTC by Gaurav
Modified: 2011-09-12 10:41 UTC (History)
4 users (show)

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

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

Description Gaurav 2011-04-08 10:58:26 UTC 
Mac host does mount using MOUNT3 but it send MOUNT1_DUMP for showmount,
713	65.541221	192.168.1.21	192.168.1.44	MOUNT	V1 DUMP Call

There is a bug in NFS server implementation to handle MOUNT1_DUMP, we are maintaining different states for MOUNT1 and MOUNT3.
Comment 1 Gaurav 2011-04-12 05:12:51 UTC 
Here is the comparison of Linux and Mac for Mount protocol.

               Linux                Mac
Mount          Mount3               Mount3

Umount         Umount3              Umount1(It fails in Getport Mount1 UDP)

Export         Mount3_Export        Mount1_Export

Dump           Mount3_Dump          Mount1_Dump
Comment 2 Anand Avati 2011-05-03 16:13:04 UTC 
PATCH: http://patches.gluster.com/patch/7056 in master (NFS : Maintain common state for MOUNT1 and MOUNT3.)
Comment 3 Anand Avati 2011-05-03 16:13:16 UTC 
PATCH: http://patches.gluster.com/patch/7008 in master (NFS : Use proper exit point in nfs_init_state.)
Comment 4 Anand Avati 2011-05-20 00:14:17 UTC 
PATCH: http://patches.gluster.com/patch/7057 in release-3.1 (NFS : Maintain common state for MOUNT1 and MOUNT3.)
Comment 5 Anand Avati 2011-06-01 01:54:23 UTC 
PATCH: http://patches.gluster.com/patch/7014 in release-3.1 (NFS : Use proper exit point in nfs_init_state.)
Comment 6 Saurabh 2011-06-09 08:55:01 UTC 
this bug is based on 2692, hence need to be reopened
Note You need to log in before you can comment on or make changes to this bug.