Redhat Mount.nfs Input/output Error
Contents |
com> Subject: Re: RHEL 5 & NFS Input/Output Error mount.nfs: mount(2): input/output error mount.nfs: mount system call failed Date: Tue, 19 Feb 2008 21:13:53 +0100 This message
Mount Windows Nfs Share On Linux Input Output Error
usually means that NFS server and client do not agree on the version input/output error nfs of NFS offered, however this might not be the cause of your problems. So, could you login as root to the RHEL3 boxes
Rpc: Failed To Contact Portmap
and do an: rpcinfo -p server (server=resolvable name of your RHEL5). and provide the output? Also, what are the mount options you use on the /etc/fstab file (or automount config) on the RHEL3 side to mount the home dirs from RHEL5? Do the NFS imported ls: reading directory .: input/output error nfs partitions show up in df, does it hang, display the partitions as mounted but with no util info?... GM Ryan Golhar wrote: Interstingly enough, I'm seeing the same thing - I have a RHEL 5 NFS server running and a bunch of RHEL 3 workstations mounting user home directories from the RHEL 5 server. I can ssh into the workstations but creating files gives the same Input/Output error. The server hard drives are fine BUT I do see this in /var/log/messages on every occurrence on the clients: kernel: svc: unknown version (3) I'm not able to log into the clients from the GUI so something serious is going on. References: RHEL 5 & NFS Input/Output Error From: Ryan Golhar [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn
Nfs Input Output Error Windows
more about Stack Overflow the company Business Learn more about hiring developers or
Freenas Nfs Input/output Error
posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer ls reading directory . input/output error in linux site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and https://www.redhat.com/archives/redhat-list/2008-February/msg00129.html rise to the top getting input/output error from NFS client on RHEL5 up vote 1 down vote favorite I have two RHEL5 boxes on a private network together (192.168.2.0/24) and I am trying to export a file system from one to the other but I keep getting the following error: mount.nfs: Input/output error on the client side I see this output: mount: trying 192.168.2.101 prog 100003 vers 3 prot http://serverfault.com/questions/182851/getting-input-output-error-from-nfs-client-on-rhel5 tcp port 2049 mount: trying 192.168.2.101 prog 100005 vers 3 prot tcp port 960 and on the server side I see this: Sep 20 14:14:32 omicron mountd[18739]: authenticated mount request from 192.168.2.87:635 for /srv/nfs/web (/srv/nfs/web) but that's all. I opened up iptables so that the whole 192.168.2.0/24 network is allowed to communicate freely but the public side is locked down to 22,80 etc.... any ideas? linux redhat nfs share|improve this question edited Jun 27 '12 at 12:41 Josh 4,791155799 asked Sep 20 '10 at 14:19 Andrew Watson 9112 add a comment| 5 Answers 5 active oldest votes up vote 1 down vote I had a similar problem, please have a look at this link. And this one. Basically you have to open much more ports. share|improve this answer answered Sep 20 '10 at 14:26 ringø 3,21531938 add a comment| up vote 1 down vote Make sure portmapper is running On centos chkconfig --list | grep portmap To start it on centos and set it to start at boot service portmap start chkconfig portmap on share|improve this answer edited Jun 27 '12 at 12:40 Josh 4,791155799 answered Apr 9 '12 at 21:11 Jason 111 add a comment| up vote 1 down vote For a similar probl
trying to mount a NFS shared folder on CentOS 6.4 from CentOS 5.9 and found a really tricky problem. I've added the /etc/fstab entry, but once I ran https://gerrydevstory.com/2013/11/12/mount-nfs-inputoutput-error-when-mounting-from-centos-5-9-to-6-4/ mount /my/folder it stuck for 2-3 minutes and came back saying mount.nfs: https://www.veritas.com/support/en_US/article.000014713 Input/output error Things I've Tried This is all the things I've tried with no success: Ensured network connection was ok. I checked the firewall / iptables and made sure the client machine can connect to NFS server Checked my /etc/hosts file, ensured no dodgy entries Double checked /etc/exports and ran exportfs output error -r on the NFS server Ran showmount -e [host_ip] to check the NFS server really does advertise the shared folders Ran rpcinfo -p [host_ip] to check the version and supporting services are available Rebooting the server many times Solution Thanks to this post from linuxquestion.org forum, the solution was to add nolock option to the /etc/fstab file. 10.0.10.10:/my/folder /mnt/nfs/my/folder nfs nolock 0 0 CentOS input output error manual is pretty vague as well on what this option really does, but oh well it seems to do the job for time being nolock — Disables file locking. This setting is occasionally required when connecting to older NFS servers. centosnfs Post navigation Previous PostCentOS / RHEL NFS Share Network Folder MountingNext PostBinding a List Request Parameter on Spring MVC Leave a Reply Cancel reply Gerry's software development journey of trial, errors and re-trials Sponsored Content Recent Posts Google Chrome Taking 16GB of my Macbook Air Managing Spring Security User Session Why You Should Use Java 8: NullPointerException Free Object Access Using Optional Using ZeroMQ Java Binding ZeroMQ Windows Java Binding: Building libzmq.dll, jzmq.dll and zmq.jar Using Visual Studio 2012 Archives Archives Select Month November 2015 August 2015 July 2015 April 2015 March 2015 February 2015 January 2015 December 2014 November 2014 October 2014 August 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 September 2013 August 2013 July 2013 June 2013 May 2013 March 2013 September 2012 August 2012 July 2012 June 2012 May 2012 Sponsored Content Proudly powered by WordPress
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet An error occurs while mounting nfs share in SRD mode for RHEL 5.7 Article:000014713 Publish: Article URL:http://www.veritas.com/docs/000014713 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem While mounting nfs share in Symantec Recovery Disk (SRD) mode for RHEL 5.7, the following error occurs: mount: Mounting [machineip]:/mnt/nfs on /mnt/nfs failed : Input/output error Error Message mount: Mounting [machineip]:/mnt/nfs on /mnt/nfs failed : Input/output error Cause By default, in RHEL 5.7 recovery disk environment, the rpc.statd that is required by NFS for remote locking may not be running. In this situation, do local locking using the -o nolock option to connect to NFS share for accessing the recovery points. Solution Run the mount command with the “-o nolock” option using the following syntax: #mount -t nfs -o nolock [MachineIP]:/mnt/nfs /tmp/nfsApplies ToRed Hat Enterprise Linux 5.7 Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the t