- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NFS write error
Operating System - HP-UX
1819794
Members
3374
Online
109607
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
Discussions
Discussions
Discussions
Forums
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
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
тАО05-31-2001 12:41 AM
тАО05-31-2001 12:41 AM
NFS write error
Hi All,
I have a Sun E450 server where users with home directories on an HPB1000 m/c log in. The setup has NIS, DNS and NFS.
I notice that the "/var/adm/messages" file is getting piled up with the foll error:
May 31 13:07:03 condor unix: NFS write error on host berkeley: error 145.
May 31 13:07:03 condor unix: (file handle: 40000004 ffffffff a0000 b60b4 5 a0000 2 0)
May 31 13:07:03 condor unix: NFS write failed for server berkeley: error 5 (RPC: Timed out)
May 31 13:07:03 condor unix: NFS write error on host berkeley: error 145.
The user home directories are mounted via NFS automounts; I do not face any problem doing NFS writes though the "messages" file keeps piling up. Sometimes the errors may be displayed on the user terminal.
Could you suggest a solution?
Thanks and regards,
Shivakumar
I have a Sun E450 server where users with home directories on an HPB1000 m/c log in. The setup has NIS, DNS and NFS.
I notice that the "/var/adm/messages" file is getting piled up with the foll error:
May 31 13:07:03 condor unix: NFS write error on host berkeley: error 145.
May 31 13:07:03 condor unix: (file handle: 40000004 ffffffff a0000 b60b4 5 a0000 2 0)
May 31 13:07:03 condor unix: NFS write failed for server berkeley: error 5 (RPC: Timed out)
May 31 13:07:03 condor unix: NFS write error on host berkeley: error 145.
The user home directories are mounted via NFS automounts; I do not face any problem doing NFS writes though the "messages" file keeps piling up. Sometimes the errors may be displayed on the user terminal.
Could you suggest a solution?
Thanks and regards,
Shivakumar
Try...try... till your system crashes!
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2001 01:27 AM
тАО05-31-2001 01:27 AM
Re: NFS write error
error 5 is I/O error , may be at that time the NFS server is not available or got network problem.
enjoy any little thing in my life
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2001 03:32 AM
тАО05-31-2001 03:32 AM
Re: NFS write error
Hi !
Thanks for the response. But the error messages are continous causing the root file system to get full if I do not keep tab. The root just has about 90 MB free and the error messages are continous. The error no. is 145 and not 5. Should that give a clue? The network is perfect.
Maybe there is some patch??
Regards,
Shivakumar
Thanks for the response. But the error messages are continous causing the root file system to get full if I do not keep tab. The root just has about 90 MB free and the error messages are continous. The error no. is 145 and not 5. Should that give a clue? The network is perfect.
Maybe there is some patch??
Regards,
Shivakumar
Try...try... till your system crashes!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2001 08:48 AM
тАО05-31-2001 08:48 AM
Re: NFS write error
There are a few areas to look:
is it always the same filehandle? It is possible that there was an interrupted system call (due to a server crash/reboot) and the client still has the old file handle.
Are you *sure* the network is not an issue?
(try running nfsstat -c on the client and look at the number of retransmissions. If it is over 5% of total calls, this indicates a problem with the transmission. Next ,zero out the counters with nfsstat -z then let it run a while, then re-run nfsstat -c.)
Look at system load on the server (and client). The server may not run enough nfsd processes if it is a very busy NFS box. The client might need more biod daemons if it is unable to keep up with the I/O on ot's end.
Just some places to look...
Jim
is it always the same filehandle? It is possible that there was an interrupted system call (due to a server crash/reboot) and the client still has the old file handle.
Are you *sure* the network is not an issue?
(try running nfsstat -c on the client and look at the number of retransmissions. If it is over 5% of total calls, this indicates a problem with the transmission. Next ,zero out the counters with nfsstat -z then let it run a while, then re-run nfsstat -c.)
Look at system load on the server (and client). The server may not run enough nfsd processes if it is a very busy NFS box. The client might need more biod daemons if it is unable to keep up with the I/O on ot's end.
Just some places to look...
Jim
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP