Bug 3867 - knfsd does not allow non-linux machines to mount exports.
Summary: knfsd does not allow non-linux machines to mount exports.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: knfsd
Version: 6.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-07-02 13:09 UTC by milburn
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-07-02 13:32:19 UTC


Attachments (Terms of Use)

Description milburn 1999-07-02 13:09:48 UTC
I recently upgraded from 5.0 -> 6.0. Before the upgrade I
had /home exported to a number of SunOS5.6,Digital Unix 4.0,
and IRIX 6.2,6.5 machines. I could have my home directory
autmount without any problems before the upgrade. After
the upgrade I couldn't even do an automount. I tried
all of the flags I could including vers=2 and nothing
seemed to work.

I removed the knfs rpm's and installed the following two
rpm's from the 5.2 package.

nfs-server-clients-2.2beta29-7
nfs-server-2.2beta29-7

This immediately fixed my problem. I then thought it might
be a problem in upgrading from RedHat5.0 -> 6.0 so I
reformatted the harddrive and did a fresh install. I still
could not mount the exported linux filesystems on any
platform but linux.

I don't know what is different about the knfsd package but
something is missing.

Please let me know how to fix this.

Comment 1 Jeff Johnson 1999-07-02 13:32:59 UTC
knfsd advertises but does not support NFSv3. There is some obscure
bug that prevents automatic fall back to NFSv2. Meanwhile, the
workaround is to not advertise NFSv3 at all. Add the flag in the
appropriate place in /etc/rc.d/init.d/nfs to look like
        ...
        echo -n "Starting NFS mountd: "
        daemon rpc.mountd --no-nfs-version 3
        echo

You might also want to look at the knfsd package at rawhide.redhat.com
which includes this fix and possibly others.


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