rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] rdiff-backup Input/output error


From: Thomas S. Dixon
Subject: Re: [rdiff-backup-users] rdiff-backup Input/output error
Date: Fri, 27 Aug 2004 12:35:39 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

Thank you very much for the reply. You were absolutely right, the problem was a lower-level filesystem problem. I had a corrupted partition somehow. Once i recreated and reformatted the partition, restored the rdiffs from tape again, it worked like a charm.

-tommy

Martin Pool wrote:
On 17 Aug 2004, "Thomas S. Dixon" <address@hidden> wrote:

Greetings all,
I have 2 questions, but first some background. We've been using rdiff-backup for about 6 months and it's been fantastic. Unfortunately, we lost some disks in our storage enclosure (which held the rdiffs) and had to start from scratch. I have now restored the rdiffs back to the enclosure from tape. Rdiff-backup lists all the increments fine. However, now I'm trying to run a subsequent backup to the restored rdiff-backup location and it errors immediately. I believe that the pertinent error is this:

OSError: [Errno 5] Input/output error: '/backup/yellowstone/rdiff-backup-data/rdiff-backup.tmp.0'

So I have 2 questions. First, what is the function of this rdiff-backup.tmp.0 file? I'm guessing it's a temp file used only by rdiff-backup during a backup. My first thought were permissions, maybe rdiff-backup couldn't create this file, but I was able to create it manually. Second question is: What kinds of things might cause this OSError? I've already looked at permissions and they seem fine.


Hi,

Errno 5 is EIO = "input/output error". (At least it is on Linux, and
many others, and that'd be consistent with this message.)  This
usually indicates an actual IO error, i.e. a problem with the
filesystem or device rather than a permissions problem.  Seeing it
often spoils your day. :-/

So I would carefully check if there are any problems with the device
you're trying to send to: run an fsck; do similar checks; check the
kernel logs; etc.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]