[Bug 304659] Re: rdiff-backup crashed with IOError in read()
Marking Fix Released since rdiff-backup 1.2.5-1 is now in Jaunty ** Changed in: rdiff-backup (Ubuntu) Status: Fix Committed = Fix Released -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
** Tags removed: need-duplicate-check -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
I have now added /sys to my exclude list, but it's good to see 1.2.3 will handle this case and I look forward to its release. Marking Fix Committed since the fix exists in upstream CVS. Thanks Andrew for your great work yet again :-) ** Changed in: rdiff-backup (Ubuntu) Status: New = Fix Committed -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
Hew, I have to tell you: If you are really getting the exact same error IOError: [Errno 110] Connection timed out with the same traceback, then I don't see how the problem can't be in rdiff-backup. The problem is occurring while it is reading from a file. Do you upgrade *anything* else when you do this upgrade? Python? librsync? Or do you truly only replace the rdiff-backup package? Here's how you can help track this down: run rdiff-backup with the -v5 option to increase verbosity. Then, rdiff-backup will print the name of each file it is working on. The last file which it is working on is our culprit. Andrew -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
don't see how the problem *can* be in rdiff-backup. :-) -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
I truly only replace the rdiff-backup package. It looks like it's having a problem in /sys. Excluding this directory results in a successful backup. I have attached the -v5 log of the problem. ** Attachment added: rdiff-backup-v5.log.gz http://launchpadlibrarian.net/20579321/rdiff-backup-v5.log.gz -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
Right, /sys shouldn't be backed-up. :-) So, why did 1.1.16 pass over this problem, and 1.2.2 choke? In 1.1.16, it failed to read any information about the files in /sys, and thus skipped over it. By 1.2.2, some bugs had been fixed to make rdiff-backup better able to read information about troublesome files (Unicode files, for example, often present the same error codes as the /sys files give when reading the file metadata). The strange thing is, when you try to get information about files in /sys, you get an Invalid file (EINVAL) error code, which rdiff-backup has long been able to handle. But when you try to actually read some of the files in /sys, then you get a Connection timed out (ETIMEDOUT) error, which rdiff-backup didn't know about. Based on your bug report, I added handling for the ETIMEDOUT error to CVS the other day. Rdiff- backup 1.2.3 will be able to pass through the /sys directory, just as 1.1.16 did. So, the correct solution is to follow the good practice of not backing- up /sys (just like /proc or /dev/shm, etc.), but rdiff-backup will no longer be tripped-up starting again with 1.2.3. Thanks, Andrew -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
I have just upgraded back to 1.2.2-1 and the exact same error is occuring. This is very reproducible, occurring all the time with 1.2.2-1, and never with 1.1.16-2. Please let me know what further information would be useful, I am happy to continue testing. -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
Hew, I don't think the version of rdiff-backup is connected to this problem; the fact that you downgraded and it worked again was probably only a coincidence. The error message indicates that the backup process Timed Out while reading a file. Unfortunately, I haven't seen that situation give that error message before (it used to be a generic I/O error), and thus you got a traceback instead of a helpful message. I have updated CVS so that it gives a human-readable message. Andrew -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
I reproduced the problem when trying to run the backup again. Downgrading to rdiff-backup 1.1.16-2 (Intrepid version) and trying again completed the backup successfully. I haven't seen anything that says compatibility is intentionally broken, and in any case a crash should not occur. -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304659] Re: rdiff-backup crashed with IOError in read()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/20158542/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/20158543/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/20158544/ProcStatus.txt ** Attachment added: Traceback.txt http://launchpadlibrarian.net/20158545/Traceback.txt ** Visibility changed to: Public ** Changed in: rdiff-backup (Ubuntu) Importance: Undecided = Medium -- rdiff-backup crashed with IOError in read() https://bugs.launchpad.net/bugs/304659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
