HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NFS problem
Operating System - HP-UX
1833322
Members
2952
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2004 06:24 AM
06-21-2004 06:24 AM
NFS problem
When i try to unmount from my HP-UX server i get these error messages. Can anyone throw some light on the same.
#umount prodsis2:/bigftp/flashemd
nfs umount: bindresvport: t_errno = 8
nfs umount: inform_server: Couldn't bind to a reserved port, rtn = -1
hawaii:/prodsis2/bigftp: umount prodsis2:/sis/data/prod/hostwkst/reman
nfs umount: bindresvport: t_errno = 8
nfs umount: inform_server: Couldn't bind to a reserved port, rtn = -1
#umount prodsis2:/bigftp/flashemd
nfs umount: bindresvport: t_errno = 8
nfs umount: inform_server: Couldn't bind to a reserved port, rtn = -1
hawaii:/prodsis2/bigftp: umount prodsis2:/sis/data/prod/hostwkst/reman
nfs umount: bindresvport: t_errno = 8
nfs umount: inform_server: Couldn't bind to a reserved port, rtn = -1
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2004 06:33 AM
06-21-2004 06:33 AM
Re: NFS problem
Could you please post the contents of nsswitch.conf?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2004 06:38 AM
06-21-2004 06:38 AM
Re: NFS problem
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start
then try unmount it.
Anil
/sbin/init.d/nfs.client start
then try unmount it.
Anil
There is no substitute to HARDWORK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2004 12:16 AM
06-22-2004 12:16 AM
Re: NFS problem
Hello,
The root of this issue appears to be the lack of available ports. umount needs to temporarily use a port in the reserved range (512- 1023) when doing the umount.
There is a known problem when using NIS as your primary name resolution resource.
Reserved ports are kept open by NIS until the calling process exits (typically
telnetd, rlogind, etc). A manual NFS mount or umount will request a port only for the
duration of the mount/umount process and then exit. Unfortunately this fails if no
ports are available. This can be seen with lsof
lsof -i UDP:512-1023 /* shows all ports 512 - 1023 in use */
Workaround: Do not use NIS as your primary / first policy for hosts: in nsswitch.conf.
You DNS or /etc/hosts would need to be able to resolve your NFS hosts.
This is resolved in HPUX 11.23
I'm not certain if this is your issue, but if it is test the workaround.
Hope this helps,
Todd
The root of this issue appears to be the lack of available ports. umount needs to temporarily use a port in the reserved range (512- 1023) when doing the umount.
There is a known problem when using NIS as your primary name resolution resource.
Reserved ports are kept open by NIS until the calling process exits (typically
telnetd, rlogind, etc). A manual NFS mount or umount will request a port only for the
duration of the mount/umount process and then exit. Unfortunately this fails if no
ports are available. This can be seen with lsof
lsof -i UDP:512-1023 /* shows all ports 512 - 1023 in use */
Workaround: Do not use NIS as your primary / first policy for hosts: in nsswitch.conf.
You DNS or /etc/hosts would need to be able to resolve your NFS hosts.
This is resolved in HPUX 11.23
I'm not certain if this is your issue, but if it is test the workaround.
Hope this helps,
Todd
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP