Linux Df Input Output Error
Contents |
LINUX HOWTO | 2 Replies More Bad Disk This article I am trying to explain how to deal with " Input/output error " reading directory input output error linux when you initiate any commands in Linux. I have pointed some examples that
Linux Bash: Input/output Error
reports similar error. # du -bash: /usr/bin/du: Input/output error #mkdir sampledir mkdir: cannot create directory `sampledir': Input/output error Input/output error while input/output error centos running the command mostly due to 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 mkdir: cannot create directory : input/output error any disk related alerts (might see some sense 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
Linux Input Output Error Deleting File
system. Good if you already have it :-). If you have good backup 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 De
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat input/output error kali linux Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red input/output error ubuntu Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red
-bash: /root/.bash_profile: Input/output Error
Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid http://linoxide.com/how-tos/inputoutput-error-bad-blocks-how-to-restart-linux/ Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical https://access.redhat.com/solutions/364334 Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences
after time Pages: 1 #1 2014-09-16 13:51:35 Carl Karl Member Registered: 2013-06-12 Posts: 225 [solved] NFS: "ls: https://bbs.archlinux.org/viewtopic.php?id=187131 reading directory .: Input/output error" after time Hello,I got the following configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via 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, the output error 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 via commandline: input output error $ 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 about your usage of ri