Failed Input/output Error Rsync
Contents |
Forums Dedicated Server Rsync input/output error - bad disk or corrupt file? If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above rsync input output error 5 to proceed. To start viewing messages, select the forum that you want to visit from the rsync read errors mapping input output error 5 selection below. Results 1 to 7 of 7 Thread: Rsync input/output error - bad disk or corrupt file? Tweet Thread Tools Show Printable Version Subscribe volume erase failed input output error to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 06-25-2011,11:52 PM #1 chasebug View Profile View Forum Posts View Forum Threads Web Hosting Master Join Date Apr 2009 Posts 1,320 Rsync final close failed input output error input/output error - bad disk or corrupt file? Sender have 602G Destination now have 600G Missing 2G of data after RSYNC. The RSYNC stops with this error: Code: ERROR: filename failed verification -- update discarded. rsync: read errors mapping "filename": Input/output error (5) rsync error: some files could not be transferred (code 23) at main.c(1298) The file is about 400MB, when I try to move the file in SSH, I get a not found error. When trying to download the file, the
Siocgmiireg On Eth0 Failed Input Output Error
file download stops at 250MB. So most likely this file is lost? And should I be worried if this disk is bad or not? The RSYNC stops running after this error, is there a command to make it skip this file and continue running RSYNC? Reply With Quote 0 06-26-2011,12:15 AM #2 chasebug View Profile View Forum Posts View Forum Threads Web Hosting Master Join Date Apr 2009 Posts 1,320 I finished RSYNC on another server but sender/destination file size are different, off by 1G total. Is this normal? When I compared the folders, the folder size are different. Folder1 sender is empty but SSH lists the folder size as 4.0K Folder1 destination is empty and SSH lists the folder size as 0K Folder2 sender have exactly 200 files and folder size of 837M Folder2 destination have exactly 200 files but folder size of 835M Reply With Quote 0 06-26-2011,01:12 AM #3 CH-Shaun View Profile View Forum Posts View Forum Threads Web Hosting Master Join Date Jun 2007 Location Australia Posts 819 Originally Posted by chasebug Sender have 602G Destination now have 600G Missing 2G of data after RSYNC. The RSYNC stops with this error: Code: ERROR: filename failed verification -- update discarded. rsync: read errors mapping "filename": Input/output error (5) rsync error: some files could not be transferred (code 23) at main.c(1298) The file is about 400MB, when I try to move the file in SSH, I get a n
Prev Next This bug is not in your last search results. Bug5246 - rsync fails to transfer some files Summary: rsync fails to transfer some files Status: RESOLVED WORKSFORME Product:
Set Scan Parameters Failed Input Output Error
rsync Classification: Unclassified Component: core Version: 2.6.9 Hardware: Other Mac OS X Importance: P3 normal disk erase failed input output error mac TargetMilestone: --- Assigned To: Wayne Davison QA Contact: Rsync QA Contact URL: Keywords: Depends on: Blocks: Show dependency tree /graph rsync failed verification update discarded Reported: 2008-02-06 16:05 UTC by david-bo Modified: 2008-02-09 12:16 UTC (History) CC List: 0 users See Also: Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or http://www.webhostingtalk.com/showthread.php?t=1060089 make changes to this bug. Description david-bo 2008-02-06 16:05:29 UTC When I use rsync to sync my music library (mp3s typically have spaces and other slightly odd characters in their names) from one intel-Mac running latest version of Mac OS X 10.4 to an external firewire drive connected to a PPC-Mac with the same OS version, rsync succesfully transfered a few hundreds of new file and verified several thousands of old files. However, https://bugzilla.samba.org/show_bug.cgi?id=5246 it choked on a few folders with the following error message: building file list ... 8435 files to consider ./ .DS_Store 15364 100% 13.98MB/s 0:00:00 (xfer#1, to-check=8433/8435) Kid Down/ /Kid Down/.DS_Store 6148 100% 136.45kB/s 0:00:00 (xfer#2, to-check=7745/8435) rsync: recv_generator: failed to stat "/Volumes/music/Tied & Tickled trio/Aelita/08. Aelita 3.mp3": Input/output error (5) rsync: recv_generator: failed to stat "/Volumes/music/Tremolo Beer Gut/.DS_Store": Input/output error (5) Tremolo Beer Gut/From The Vinyl Archives Of/ rsync: recv_generator: mkdir "/Volumes/music/Tremolo Beer Gut/From The Vinyl Archives Of" failed: Input/output error (5) *** Skipping everything below this failed directory *** Tremolo Beer Gut/The Inebriated Sound Of The Tremolo Beer Gut/ rsync: recv_generator: mkdir "/Volumes/music/Tremolo Beer Gut/The Inebriated Sound Of The Tremolo Beer Gut" failed: Input/output error (5) *** Skipping everything below this failed directory *** Emmaboda 2007.3/ Comment 1 Matt McCutchen 2008-02-06 16:11:28 UTC An "Input/output error" generally indicates a problem with the filesystem, operating system, or hardware, not with rsync. If you "stat" the problematic files manually at the shell, does that succeed? Can "cp" copy the files? Comment 2 david-bo 2008-02-07 16:47:42 UTC I could copy the files both with cp and using the GUI. I could also stat the files without any obvious error. Furthermore, I tested copying the directories in the receiving location, They where, not surprisingly, empty and duplicating them using cp ap
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 http://serverfault.com/questions/312076/read-errors-backing-up-to-nfs-via-rsync Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. 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 Read Errors Backing Up To NFS via rsync up vote 1 down output error vote favorite I'm backing up a linux box to a NAS mounted via NFS. I'm using rsync (as part of a scheme along the lines of http://www.mikerubel.org/computers/rsync_snapshots/ with hard-links). That is I ssh into machine_being_backed_up, start my rsync command, it backs up files for about an hour or so, and then freezes the server (e.g., needs to be physically rebooted; which is very inconvenient as the servers in another building across town so takes time to input output error reboot) the error at the end being (with actual names anonymized): some/path/file1.gz rsync: read errors mapping "/home/some/path/file1.gz": Input/output error (5) some/path/file2.gz rsync: read errors mapping "/home/some/path/file2.gz": Input/output error (5) some/path/file3.gz This is likely indicating that the hard drive on the machine I'm trying to back up has some faulty sectors, correct? Or could that error arise from the NFS connection being too slow or choosing the wrong options when mounting my NFS drive (mounting with rw,soft,intr options)? Is there anyway to make these input/output errors just skip/fail those files, and not freeze the system (so I don't have to go across town to reboot the server)? Update: I turned on SMART yesterday and ran short and long selftests yesterday that reported no errors (yesterday I couldn't mention this as the long test finished around 7p and the computer crashed around midnight so I could login until this morning when I could on-site reboot). Also I tried rsync-ing the in question files to a different partition on the same drive and didn't get any errors. I'm now trying to rsync directly to the NAS (rather than mounting the NAS using NFS). Update (Oct 3rd): I've moved the hard drive to a different machine and its been ~2 weeks with no errors. While in the old machine there were daily errors of this type. I'm guessing motherboard or memory e