Mount.nfs Input Output Error
Contents |
after time Pages: 1 #1 2014-09-16 13:51:35 Carl Karl Member Registered: 2013-06-12 Posts: 225 [solved] NFS: "ls: reading directory .: Input/output error" after
Mount.nfs Input/output Error Rhel5
time Hello,I got the following configuration:NFS-server: Always on, connected via LAN.NFS-clients: ls reading directory . input/output error in linux 2 computers, connected via LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with ls: reading directory .: input/output error nfs systemd.This works flawlessly some hours or even days. But after some time, the following happens:1. mount nfs-share: no error message2a. trying to access that folder via
Input/output Error Linux
filemanager, e.g. thunar: folder seems to be empty (it isn't on server!), but the correct freesize of the NFS-share on server is displayed in the statusbar.2b. trying to access that folder via commandline: $ ls ls: reading directory .: Input/output errorThe very same worked just a few hours before, I haven't changed anything
Rpc: Failed To Contact Portmap
meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual mount NFS-share) on the clients which worked before, too.Any idea what's going wrong?additional info:server: /etc/exports _______________________ /srv/nfs/myshare 192.168.2.0/24(rw,all_squash,anonuid=33,anongid=33,no_subtree_check)(yes, the mapping is needed and right.)clients:/etc/fstab _______________________ servername:/srv/nfs/myshare /home/carl/nfs nfs4 noauto,soft,user,_netdev,timeo=14,rsize=8192,wsize=8192 0 0/usr/lib/systemd/system-sleep/umount-nfs _______________________ #!/bin/sh case $1 in pre) umount -f /home/carl/nfs ;; esac Last edited by Carl Karl (2014-09-21 17:07:47) Offline #2 2014-09-16 14:15:27 nomorewindows Member Registered: 2010-04-03 Posts: 3,015 Re: [solved] NFS: "ls: reading directory .: Input/output error" after time Somehow your nfs mounts have gone stale. You'd need to remount them or restart nfs related services. Dmesg or syslog output may help. I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...Look ma, no mouse. Offline #3 2014-09-16 14:29:10 Carl Karl Member Registered: 2013-06-12 Posts: 225 Re: [solved] NFS: "ls: reading directory .: Input/output error" after time Indeed, there could be something interesting in dmesg on the server:[ 4.1
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss mount windows nfs share on linux input output error the workings and policies of this site About Us Learn more about
Nfs Input Output Error Windows
Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions mount nolock example Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's https://bbs.archlinux.org/viewtopic.php?id=187131 how it works: Anybody can ask a question Anybody can answer The best answers are voted up and 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 http://serverfault.com/questions/182851/getting-input-output-error-from-nfs-client-on-rhel5 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 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,791145799 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,21031938 add a comment| up vote 1 down vote Make sure portmapper is r
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME https://ubuntuforums.org/showthread.php?t=1474797 Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter https://www.veritas.com/support/en_US/article.000014713 Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search output error Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Networking & Wireless [ubuntu] NFS mounting fails (mount(2): Input/output error, mount system call failed) Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to input output error 2 of 2 Thread: NFS mounting fails (mount(2): Input/output error, mount system call failed) Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 6th, 2010 #1 bjtuna View Profile View Forum Posts Private Message Visit Homepage A Carafe of Ubuntu Join Date Jul 2005 Location Boise, Idaho, USA Beans 111 DistroUbuntu 12.04 Precise Pangolin NFS mounting fails (mount(2): Input/output error, mount system call failed) I have been using Ubuntu for several years now. I have always had the following line in /etc/fstab: Code: 192.168.0.30:/shares/SimplePool/Storage /home/brian/Storage nfs rw,auto,rsize=8192,wsize=8192,intr,soft,retry=5 0 0 That, along with having Code: nfs-common installed, has always worked great for accessing my remote NFS server. Unfortunately Ubuntu 10.04 (Lucid) isn't cooperating. If I try to manually mount /home/brian/Storage it will hang. I ran the following equivalent command to debug: Code: sudo mount -v -t nfs -o rw,auto,rsize=8192,wsize=8192,intr,soft,retry=5 192.168.0.30:/shares/SimplePool/Storage /home/b
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