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 .: Input/output ls reading directory . input/output error ubuntu error" after time Hello,I got the following configuration:NFS-server: Always
Ls Reading Directory . Input/output Error Centos
on, connected via LAN.NFS-clients: 2 computers, connected via LAN and WLAN. On standby: auto umount ls reading directory . input/output error redhat 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: no error message2a. trying
Ls Cannot Access Input/output Error
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 .: Input/output errorThe very same worked just input/output error mac 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 Member Registered: 2013-06-12 Posts: 225 Re: [solved] NFS: "ls: reading directory
/ Output Error with USB Drive Issues related to hardware problems Post Reply Print view Search Advanced search 7 posts • Page 1 of 1 crock Posts: 6 Joined: 2014/07/22 13:41:40 [SOLVED]
"input/output Error" Nfs
Input / Output Error with USB Drive Quote Postby crock » 2014/11/20 12:58:33
Input Output Error While Copying Linux
500GB Seagate USB Hard Drive - attempting to mount it on my Centos 6.6 box. I want to be very cannot open directory . input/output error clear - this drive works 100% flawlessly on other machines (both windows and other linux flavors)During mount attempts, I'm getting Input/Output Errors. I have no idea what I'm doing wrong here.I've got the https://bbs.archlinux.org/viewtopic.php?id=187131 following packages installed directly from EPEL:Code: Select all(1/2): ntfs-3g-2014.2.15-6.el6.x86_64.rpm | 258 kB 00:00
(2/2): ntfsprogs-2014.2.15-6.el6.x86_64.rpm | 235 kB 00:00
I can use the following command to mount it (and it mounts successfully):Code: Select all$ sudo ntfs-3g /dev/sdd1 /mnt/usbI just cannot read or write anything to it.Code: Select all$ ls /mnt/usb
ls: reading http://www.centos.org/forums/viewtopic.php?t=49718 directory .: Input/output errorI however *CAN* write to it on my Fedora20 and Windows7 boxes. Can anyone give me an idea as to what I'm doing wrong? The Fedora20 box has the same RPMs installed.I have the Seagate Diagnostic tools installed on my Windows7 box and it passes every single diagnostic test.I have even zero'd the thing out, reformatted NTFS and still no luck. Any help is appreciated! Last edited by crock on 2014/11/21 12:16:09, edited 1 time in total. Top aks Posts: 1980 Joined: 2014/09/20 11:22:14 Re: Input / Output Error with USB Drive Quote Postby aks » 2014/11/20 17:11:40 I had this one recently. I had previously installed the ntfs fuse driver via rpmforge (naughty me) and I ended up having to remove it, disable rpmforge and install all the nfs stuff from elrepo - then it worked fine. I think the rpmforge fuse driver was "marked" as a later version than the EPEL one, so yum installed that everytime until I disabled rpmforge. Exact same symptoms (I/O error).But if you're 100% sure you got it from EPEL, then tha's a different story. Top TrevorH Forum Moderator Posts: 16763 Joined: 2009/09/24 10:40:56 Location: Brighton, UK Re: I
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 http://stackoverflow.com/questions/18819812/ls-reading-directory-input-output-error this site About Us Learn more about Stack Overflow the company Business Learn http://askubuntu.com/questions/74105/how-do-you-repair-an-input-output-error-in-an-ntfs-partition 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 output error 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 directory . input/output 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,6841059103 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 spe
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 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 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 How do you repair an “input/output error” in an NTFS partition? up vote 26 down vote favorite 13 I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get: Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read NTFS $Bitmap: Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu? windows ntfs share|improve this question edited May 15 at 19:06 muru 68.3k12125172 asked Oct 31 '11 at 15:13 Calixte 67951528 add a comment| 5 Answers 5 active oldest votes up vote 17 down vote accepted chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk. If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer). There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives. share|improve this answer answered Oct 31 '11 at 15:24 O