- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NFS Client on HPUX / NFS Server Redhat
Operating System - HP-UX
1753531
Members
5430
Online
108795
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
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
тАО11-09-2010 06:38 PM
тАО11-09-2010 06:38 PM
NFS Client on HPUX / NFS Server Redhat
Have a issue where files are dropped on redhat server file system that is exported via NFS to a hp-ux 11.23 server. the hp-ux server mounts the nfs client file system. So sometimes like last nite 5 files where placed on the linux file system and all are seen, BUT when you go to the corresponding hp-ux server and look at the client mount only 3 of 5 were visible! Now if you 'touch' a file on the hp-ux file system in question, then do a ls... ALL 5 now are displayed. Looks like some kind of caching issue to me on NFS, that until a extra file is created the NFS cache gets flushed and all files are available on the client mount. Just not sure, but seem to have heard of this before... = help if you can. Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2010 03:18 PM
тАО11-15-2010 03:18 PM
Re: NFS Client on HPUX / NFS Server Redhat
Not sure, whether your issue resolved?
Have you checked the options you used to mount these NFS? Is this only one HPUX server utilizing NFS mount from RedHat ?
Have you checked the options you used to mount these NFS? Is this only one HPUX server utilizing NFS mount from RedHat ?
Regards
Shibin
Shibin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2010 09:43 PM
тАО11-15-2010 09:43 PM
Re: NFS Client on HPUX / NFS Server Redhat
Hi Dan,
I have heard about synchronous and asynchronous behavior of nfs exports.
Looks like you have seen it real? I just tried to search about this and see the below information.Find the nfs version you have and if you need you can enable the synchronous exports rather than keeping writes in cache and do it at a later time.
The default export behavior for both NFS Version 2 and Version 3 protocols, "asynchronous". This default permits the server to reply to client requests as soon as it has processed the request and handed it off to the local file system, without waiting for the data to be written to stable storage. This is indicated by the async option denoted in the server's export list. It yields better performance at the cost of possible data corruption if the server reboots while still holding unwritten data and/or metadata in its caches. This possible data corruption is not detectable at the time of occurrence, since the async option instructs the server to lie to the client, telling the client that all data has indeed been written to the stable storage, regardless of the protocol used.
Thanks & Regards
Jayakrishnan G Naik
I have heard about synchronous and asynchronous behavior of nfs exports.
Looks like you have seen it real? I just tried to search about this and see the below information.Find the nfs version you have and if you need you can enable the synchronous exports rather than keeping writes in cache and do it at a later time.
The default export behavior for both NFS Version 2 and Version 3 protocols, "asynchronous". This default permits the server to reply to client requests as soon as it has processed the request and handed it off to the local file system, without waiting for the data to be written to stable storage. This is indicated by the async option denoted in the server's export list. It yields better performance at the cost of possible data corruption if the server reboots while still holding unwritten data and/or metadata in its caches. This possible data corruption is not detectable at the time of occurrence, since the async option instructs the server to lie to the client, telling the client that all data has indeed been written to the stable storage, regardless of the protocol used.
Thanks & Regards
Jayakrishnan G Naik
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP