Input Output Error Linux
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 input/output error ubuntu following configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via input/output error centos LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.This works flawlessly some hours or cannot open directory . input/output error even days. 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 linux input output error deleting file (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 meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual
Input/output Error Nfs
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.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 R
LINUX HOWTO | 2 Replies More Bad Disk This article I am trying to explain how to deal with " Input/output error " when you initiate any
Input/output Error Mac
commands in Linux. I have pointed some examples that reports similar error. # du ls reading directory . input/output error centos -bash: /usr/bin/du: Input/output error #mkdir sampledir mkdir: cannot create directory `sampledir': Input/output error Input/output error while running the command mostly due to ls: cannot access input/output error two reason. Either it could be bad blocks on the disk or someone hacked your machine. In this situation first suggestion would be to check /var/log/messages for any disk related alerts (might see some sense https://bbs.archlinux.org/viewtopic.php?id=187131 key alerts). tail -n 100 /var/log/messages tail -f /var/log/messages If you notice any disk issues , try any disk utility to confirm this. One option would be use smarttools. You can check smartool option to fix bad blocks. If you already installed it you can take the advantage of that. Next immediate action would be take backup of your system. Good if you already have it :-). If you have good backup http://linoxide.com/how-tos/inputoutput-error-bad-blocks-how-to-restart-linux/ its safe to reboot.If your system was hacked there are chances they might messed up your file and system would not work after reboot. You can also try fsck but it really dont fix most time if it bad block issue. Fsck can fix only if it related to any filesystem related issues. Usually fsck will fail in between as when it try to read the file at bad block. Now if try to reboot , it can also give the same output. You can try init 6. # reboot bash: /sbin/reboot: Input/output error # shutdown -r now bash: /sbin/shutdown: Input/output error If the above reboot commands doesnot work try either forced reboot or shutdown . Forced Reboot echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger Forced Shutdown echo 1 > /proc/sys/kernel/sysrq echo o > /proc/sysrq-trigger You might also likeHow To Fix / Repair Bad Blocks In LinuxLinux Hdparm Command: Display Hard Disk Model and Serial NumberFew Tips Check Hard Disk Error and Health using smartctl6 Examples To Get Linux Hardware Details / InformationError: modprobe: Can't locate module block-major-227 Examples Linux Dmidecode Command - Display Hardware Details In BIOSHow To Backup LVM Configuration On Linux (vgcfgbackup & vgcfgrestore)Linux Crontab: How To Configure Cron With Best Examples?How To List Linux Pci Devices
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any http://askubuntu.com/questions/15476/input-output-error-drives-randomly-refusing-to-read-write questions you might have Meta Discuss the workings and policies of http://stackoverflow.com/questions/18819812/ls-reading-directory-input-output-error this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users output error and developers. 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 top input / output error, drives randomly refusing to read / write [closed] up vote 4 down vote favorite 1 I input output error have an issue with one of our servers running Ubuntu 10.04, it is running BackupPC and collects backups from various machines / servers around the building. On the 8th minute (12:08, 12:18, 12:28 etc) the backups are transferred to an external hard drive, we have three and rotate one drive for another everyday. The problem we are having is we are randomly experiencing input / output errors, when this happens you cannot read / write to the drive, it hasn't unmounted so I can cd to the mount point /media/backup1. The drives are not faulty as it's happening on all of them, so I'm at a loss as to what the problem could be, here is an example of the many errors we get: gzip: stdout: Input/output error /var/lib/backuppc/backuppc_offline: line 47: /media/backup1/Tue/offline.log: Input/output error ls: cannot access /media/backup1/Tue/incr_1083_host1.something.co.uk.tar.gz: Input/output error ls: cannot access /media/backup1/Tue/incr_1088_host1.something.co.uk.tar.gz: Input/output error ls: cannot access /media/backup1/Tue/incr_1089_host1.something.co.uk.tar.gz: Input/output error ls: cannot access /media/backup1/Tue/incr_1090_host1.something.co.uk.tar.gz: Input/output error /var/lib/backuppc/backuppc_offline: line 3
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 or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ls: reading directory .: Input/output error [closed] up vote 2 down vote favorite My system raised the I/O error when I tried to use 'ls' on a mounted hard disk. I am using hadoop@hbase1:/hddata$ uname -a Linux hbase1 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux hadoop@hbase1:/hddata$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/hbase2--vg-root 468028968 2715496 441532304 1% / udev 6081916 4 6081912 1% /dev tmpfs 2436652 336 2436316 1% /run none 5120 0 5120 0% /run/lock none 6091620 0 6091620 0% /run/shm /dev/sda1 1922727280 867279740 957771940 48% /hddata /dev/sdb1 233191 27854 192896 13% /boot 10.18.103.101:/data/marketdata 1883265024 1644255232 143344640 92% /srv/data/marketdatah The last several lines of dmesg hadoop@hbase1:/hddata$ dmesg | tail [316263.280056] EXT4-fs (sda1): previous I/O error to superblock detected [316263.281326] sd 0:0:0:0: [sda] Unhandled error code [316263.281329] sd 0:0:0:0: [sda] [316263.281330] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [316263.281332] sd 0:0:0:0: [sda] CDB: [316263.281334] Write(10): 2a 00 00 00 00 3f 00 00 08 00 [316263.281342] end_request: I/O error, dev sda, sector 63 [316263.282584] Buffer I/O error on device sda1, logical block 0 [316263.283799] lost page write due to I/O error on sda1 [316263.283842] EXT4-fs error (device sda1): ext4_find_entry:1270: inode #2: comm bash: reading directory lblock 0 linux filesystems share|improve this question edited Apr 4 '14 at 18:54 Tshepang 4,6941059103 asked Sep 16 '13 at 2:56 Vimos 1021211 closed as off-topic by Duck, wudzik, Yu Hao, JB., Kjuly Sep 16 '13 at 9:37 This question appears to be off-topic. The users who voted to close gave this specific reason:"Questions about general computing hardware and software are off-topic for Stack Overflow unless they directly involve tools used primarily for programming. You may be able to get help on Super User." – Duck, wudzik, Yu Hao, JB., KjulyIf this question can be reworded to fit the rules in the help center, please edit