Inputoutput 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: input/output error ubuntu "ls: reading directory .: Input/output error" after time Hello,I
Input/output Error Centos
got the following configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via cannot open directory . input/output error LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.This works flawlessly some hours or even days. But after some time,
Linux Input Output Error Deleting File
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 on server!), but the correct freesize of the NFS-share on server is displayed in the statusbar.2b. trying to access that folder input/output error nfs 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 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 ab
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 commands in
Input/output Error Mac
Linux. I have pointed some examples that reports similar error. # du -bash: /usr/bin/du: Input/output
Ls Reading Directory . Input/output Error Centos
error #mkdir sampledir mkdir: cannot create directory `sampledir': Input/output error Input/output error while running the command mostly due to two reason. Either ls: cannot access input/output error 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 key alerts). tail -n https://bbs.archlinux.org/viewtopic.php?id=187131 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 its safe to reboot.If your http://linoxide.com/how-tos/inputoutput-error-bad-blocks-how-to-restart-linux/ 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 Using lspci CommandSet Date And Time In Linux And Sync With Hardwa
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 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 and output error 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 have input/output error centos 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 39: /media/backup1/Tue/offline.log: Input/outp