Ls Reading Directory 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 ls reading directory . input/output error centos .: Input/output error" after time Hello,I got the following input/output error ubuntu configuration:NFS-server: Always on, connected via LAN.NFS-clients: 2 computers, connected via LAN and WLAN. On ls: reading directory .: input/output error ext4 standby: auto umount NFS-share via system-sleep-hook with systemd.This works flawlessly some hours or even days. But after some time, the following happens:1. mount nfs-share:
Ls Reading Directory . Input/output Error Redhat
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: $ ls ls: reading directory .: cannot open directory . input/output error 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 ridiculously easy graphical interfaces...Look ma, no mouse. Offline #3 2014-09-16 14:29:10 Carl Karl
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME 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 Useful Links linux input output error deleting file Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page
Ls Cannot Access Input Output Error
Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] Input/output error when accesing a
Input/output Error Nfs
directory 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 7 of 7 Thread: Input/output error when accesing a https://bbs.archlinux.org/viewtopic.php?id=187131 directory Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October 25th, 2010 #1 tjoff View Profile View Forum Posts Private Message Just Give Me the Beans! Join Date Apr 2009 Location Denmark Beans 58 DistroUbuntu 10.04 Lucid Lynx Input/output error when accesing a directory Hi I have a directory "foo" on a NTFS partition of my hard drive, which i created a couple of days ago. After creation https://ubuntuforums.org/showthread.php?t=1605384 it worked fine and i put some files in it, but the day after i get the following error: me@mymachine:/media/disk1$ ls -l foo ls: cannot access foo: Input/output error me@mymachine:/media/disk1$ ls -l ls: cannot access foo: Input/output error total 101 d????????? ? ? ? ? ? foo (+ a succesful listing of other files and directories) I get the Input/output error no matter what i try to do to the directory (rm, mv, cd, etc.), and no matter which privileges i have. I read some threads suggesting that it is a hardware problem. I tried running ntfsfix on the partition: me@mymachine:~$ sudo ntfsfix /dev/sda3 Mounting volume... OK Processing of $MFT and $MFTMirr completed successfully. NTFS volume version is 3.1. NTFS partition /dev/sda3 was processed successfully. I have also run the short and the long SMART test from the disk utility, resulting in the overall assessment: Disk is healthy. It would be nice to know how to recover the data in the directory, but i have backup so that part is not crucial. I could also reformat the whole drive to ext4, which I eventually would have done in any case. Or i could just ignore the defective folder which does not harm anyone. However if this problem is the first warning of a failing drive, I would rather get a new drive now, before some more important data suddenly disappear. My question is now, what cour
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 http://stackoverflow.com/questions/18819812/ls-reading-directory-input-output-error 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 http://forum.doozan.com/read.php?2,4998,6481 Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ls: reading directory .: Input/output error 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 ls reading directory 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,6991059103 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 i
2011 08:44AM Registered: 6 years ago Posts: 58 Greetings I have had a Dockstar running Debian squeeze since last September. It runs rtorrent 24/7, and has worked well so far. It has a 1 TB usb hard disk with ext3 file system hooked to it. Yesterday, I got this error when trying to do ls on a directory on that usb hard disk: $ ls ls: reading directory .: Input/output error $ Huh? That sounds like a possible hardware failure, but the hard disk is only a few months old. I shut the Dockstar down, hooked the usb hard disk to another linux box, and ran fsck on it. fsck found no problems, and so I restarted the Dockstar, hooked the usb hard disk back up, and it works fine now. Any ideas what might have happened here? This is unexpected, flaky, "un-Debian-like" behavior, and has never happened before on any of my various linux machines. Reply Quote dpffan Re: Getting "reading directory .: Input/output error" June 07, 2011 09:43AM Run smartctl from the linux box and see what SMART says, ie http://en.wikipedia.org/wiki/S.M.A.R.T. Reply Quote hanker Re: Getting "reading directory .: Input/output error" June 07, 2011 05:51PM Registered: 6 years ago Posts: 58 > Run smartctl from the linux box and see what SMART > says, ie > http://en.wikipedia.org/wiki/S.M.A.R.T. Thank you for your reply :) I installed smartmontools. I ran smartctl on the drive and got this: $ sudo smartctl -i /dev/sdc smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Device: WDC WD10 EVDS-63U8B0 Version: 01.0 Serial number: WD-WCAV5F916494 Device type: disk Local Time is: Tue Jun 7 16:28:19 2011 CDT Device does not support SMART $ This is a several-month-old 1 TB Western Digital SATA drive mounted in an Icydock usb 2.0 enclosure. Hmmm... Anyway, after working fine all day, I came home and tried to mount the drive on my Mac with nfs. Like yesterday, I did the mount by double-clicking an alias to the drive. That's when it failed again. This has always worked before. I rebooted the Dockstar and it's OK again. I can mount the drive on the Mac with cmd-K and it works fine. Here's what showed up in dmesg when it failed. The first line is from the end of boot. [ 114.998173] EXT3-fs: mounted filesystem with ordered data