HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: nfs error in messages file
Operating System - Tru64 Unix
1827474
Members
2061
Online
109965
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
03-10-2005 07:54 PM
03-10-2005 07:54 PM
nfs error in messages file
Mar 11 11:11:26 ALPHAEH5 vmunix: NFS server: stale file handle fs(3614,468006) file 24880 gen 32770
Mar 11 11:11:26 ALPHAEH5 vmunix: RFS3_READ, client address = 150.0.150.3, errno 22
The server is ES40 with 5.1tru-64.
Doubting that only nfs mount was attemted from other server with ip 150.0.150.3
Has anybody faced this errorno 22.
Regards,
Akshay.Danak
Mar 11 11:11:26 ALPHAEH5 vmunix: RFS3_READ, client address = 150.0.150.3, errno 22
The server is ES40 with 5.1tru-64.
Doubting that only nfs mount was attemted from other server with ip 150.0.150.3
Has anybody faced this errorno 22.
Regards,
Akshay.Danak
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2005 10:40 PM
03-10-2005 10:40 PM
Re: nfs error in messages file
use "search" and enter "stale" "nfs".
You will get suitable answers for your problem.
You will get suitable answers for your problem.
Help() { FirstReadManual(urgently); Go_to_it;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2005 01:28 AM
03-11-2005 01:28 AM
Re: nfs error in messages file
A stale file handle can occur under many different circumstances. It is most often seen when a client attempts to access a file or files on an nfs server which may have rebooted in which case, the file handles
are no longer valid, which may account for the errno=22 which equates to an invalid argument.
I would start by looking through other log files on both the client and the server for events that might have occured around the time of the error listed.
Check to see if anything has changed recently in the network configuration or host environments for either client or server.
Check for errors on both client and server (netstat -i).
Check to see if the server has spiked in terms of cpu utilization.
Check to see if there is a difference in network interface speeds between
the client and the server and if so, see if this is a recent change.
Check to see if these are new errors or something that has been occuring
for some time.
If you can supply more information, perhaps we can be of further assistance.
are no longer valid, which may account for the errno=22 which equates to an invalid argument.
I would start by looking through other log files on both the client and the server for events that might have occured around the time of the error listed.
Check to see if anything has changed recently in the network configuration or host environments for either client or server.
Check for errors on both client and server (netstat -i).
Check to see if the server has spiked in terms of cpu utilization.
Check to see if there is a difference in network interface speeds between
the client and the server and if so, see if this is a recent change.
Check to see if these are new errors or something that has been occuring
for some time.
If you can supply more information, perhaps we can be of further assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2005 01:21 AM
03-16-2005 01:21 AM
Re: nfs error in messages file
If you are using ADVFS, you can usr /sbin/advfs/tag2name /mountpoint/.tags/24880 to convert a tag 24880 to a filename,
I have some messages, and I found that some files in shared directory are being accessing by two process in the same time .
(ie , one is copying the file and the other try to move it to another direcory)
I have some messages, and I found that some files in shared directory are being accessing by two process in the same time .
(ie , one is copying the file and the other try to move it to another direcory)
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP