Input Output Error Nfs
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 time Hello,I got the following mount.nfs input/output error rhel5 configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via LAN and ls reading directory . input/output error in linux WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.This works flawlessly some hours or even days. input/output error linux But after some time, the following happens:1. mount nfs-share: no error message2a. trying to access that folder via filemanager, e.g. thunar: folder seems to be empty (it isn't ls: reading directory .: input/output error nfs 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 meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual mount NFS-share) on the
Ls Reading Directory . Input/output Error Centos
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.190117] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 4.190596] NFSD: starting 90-second grace period (net ffffffff818a9540) [ 5.445237] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
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 more about Stack Overflow the company Business Learn more about hiring developers
Ls Reading Directory Input Output Error Ubuntu
or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server ls reading directory . input/output error redhat Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: ls: reading directory .: input/output error ext4 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 https://bbs.archlinux.org/viewtopic.php?id=187131 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 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 http://serverfault.com/questions/182851/getting-input-output-error-from-nfs-client-on-rhel5 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 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,791145799 answered Apr 9 '12 at 21:11 Jason 111 add a comment| up vote 1 down vote For a similar problem, I have added to the syntax of the mount command the following options "-o nolock, udp." mount -o nolock,udp 192.168.4.11:/var/nfs /mnt/nfs/ Apparently this problem when the service nfslook is not 'started' successfully. share|improve this answer answered Feb 28 '13 at 18:01 Valentino 111 add a comment| up vote 0 down vote Check the following: On the server, can you read/write to and from /srv/nfs/web? What's in your /etc/exports? What's in /etc/hosts.* What's in
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 more http://serverfault.com/questions/234556/nfs-server-windows-2008-mounting-via-linux-input-output-error-help about Stack Overflow the company Business Learn more about hiring developers or posting ads https://forums.freenas.org/index.php?threads/input-output-error-nfs-server-not-responding.20793/ with us Server Fault Questions 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 how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the output error top NFS server Windows 2008 - mounting via linux - input/output error help up vote 2 down vote favorite I want to try mounting a folder with NFS - I set up the NFS sharing on a windows 2008 R2 server, specified hosts in the NFS permissions (by IP address) and mounted via /etc/fstab it mounts, but when I try to list the folder, I get 'input/output error' the owner/group reading directory . on the local mount point look weird too? drwx------ 2 4294967294 4294967294 4096 2011-02-10 19:15 data/ I mounted in /etc/fstab as: 10.0.6.55:/share$ /media/data nfs soft,intr,rsize=8192,wsize=8192 What am I doing wrong? linux windows-server-2008 nfs share|improve this question asked Feb 11 '11 at 21:17 pablo 2,72511120 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted The issue was on the Windows Server side and it could not map the unix account to AD. This blog post+comments led me to the solution. http://blogs.msdn.com/b/sfu/archive/2007/04/19/mounting-nfs-share-on-nfs-client.aspx share|improve this answer answered Feb 17 '11 at 12:04 pablo 2,72511120 add a comment| up vote 1 down vote In the NFS settings in windows NFS Share settings, checking allow Unmapped users access radio box allows it to work. share|improve this answer edited Mar 10 '14 at 11:26 sysadmin1138♦ 99.5k14124253 answered Mar 10 '14 at 5:41 Brent Cetinich 111 add a comment| up vote 0 down vote UID/GID mapping can be messed up, but you could try and chown the mount to yourself share|improve this answer answered Feb 11 '11 at 21:56 dyasny 14.1k32851 tried mounting with a specific gid/uid, didnt work. any other ideas? –pablo Feb 14 '11 at 20:10 I meant mount as root, and then c
Newbie Joined: May 9, 2014 Messages: 15 Thanks Received: 0 Trophy Points: 4 Hello, I'm quite new to Freenas and BSD. With my installation I ran into the following problem. I'm using freenas nfs shares as a backup space for some servers. All my script does is mount the freenas nfs share and than use rsync to copy a few folders on a regular basis. Freenas/ZFS than does snapshots on the shares. So far so good, but what I experience is, that I get a lot of these messages: Code:rsync: readdir("/mybackup/files/files.txt"): Input/output error (5) and in dmesg: Code:nfs: server freenas.intern.lan not responding, timed out cat /proc/mounts shows the following mount options Code: nfs rw,relatime,vers=3,rsize=16384,wsize=16384,namlen=255,soft,proto=udp,timeo=60,retrans=20,sec=sys,mountaddr=172.16.4.25,mountvers=3,mountport=726,mountproto=udp,local_lock=none,addr=172.16.4.25 Any ideas on what might be the problem? I'm happy to provide more information on the setup if needed. Kai Timmer, May 9, 2014 #1 dlavigne Administrator Administrator Moderator iXsystems Joined: May 24, 2011 Messages: 6,197 Thanks Received: 304 Trophy Points: 81 Does the problem persist if you use -o tcp when mounting the share? dlavigne, May 9, 2014 #2 Kai Timmer Newbie Joined: May 9, 2014 Messages: 15 Thanks Received: 0 Trophy Points: 4 Yes, same Problem. Kai Timmer, May 9, 2014 #3 Kai Timmer Newbie Joined: May 9, 2014 Messages: 15 Thanks Received: 0 Trophy Points: 4 Anyone with another idea? Maybe someone pointing me in the right direction? I'm kinda lost here Kai Timmer, May 12, 2014 #4 cyberjock Moderator Moderator Joined: Mar 25, 2012 Messages: 19,105 Thanks Received: 1,639 Trophy Points: 161 What's your server hardware and FreeNAS version? ZFS or UFS? Can you post the script you are using? Hardware recommendations • RAID5/RAIDZ1 is dead Read my guide! It answers co