Bug 54378 - NFS mount on IBM AIX
Summary: NFS mount on IBM AIX
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-server
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-05 08:39 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-10-15 13:45:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-10-05 08:39:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
When exporting a filesystem on Linux as
/home/test name_of_aix(rw)

a mount on the AIX machine (AIX 4.3.2) results in a "Operation not 
permitted" error message. The same mount on a SUN Solaris works.
Whats wrong with the Linux-AIX connection?


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


How reproducible:
Always

Steps to Reproduce:
1./etc/exports on Linux: /home/test name_of_aix(rw)

2.On IBM AIX 4.3.2:  mount name_of_linux:/home/test /tmp/test
mount 1831-008 wird aufgegeben bei:
name_of_linux:/home/test
vmount: Die Operation ist nicht zulaessig.

3.Inside the /var/log/messages of Linux:
 localhost kernel: nfsd: request from insecure port (0ad22875:62298)!

	

Actual Results:  No filesystem is mounted. I receive only an error message.

Expected Results:  The filesystem should be mounted.

Additional info:

I think, with a special parameter inside the /etc/exports or within the 
mount request, the error can be solved. Is it possible, that I make a 
mistake?

Comment 1 Joe Orton 2001-10-15 13:45:35 UTC
Try this command from the AIX box as root:

   # nfso -o nfs_use_reserved_ports=1


Comment 2 Michael K. Johnson 2001-10-15 15:27:56 UTC
Agreed, this is a client configuration issue.  Thanks for providing
the necessary configuration change.


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