Matthias Schniedermeyer wrote:
> On 22.12.2009 19:24, Stefan Nowak wrote:
> >>> On 22.12.2009 16:39, Stefan Nowak wrote:
> >>>
> >>> The only low-budget test ideas I have:
> >>>
> >>> The CD scratching a la Tomas Gustavsson seems the only easily
> >>> achievable
> >>> solution. But then it is not
Wayne Davison (way...@samba.org) wrote on 22 December 2009 08:02:
>On Tue, Dec 22, 2009 at 4:18 AM, Tomas Gustavsson wrote:
>> Still, I do think that rsync should give up after a long time, but it
>> doesn't.
>
>Yeah, if it gets a read error for a part of a file, it substitutes
>zeros for t
On 22.12.2009 19:24, Stefan Nowak wrote:
>>> On 22.12.2009 16:39, Stefan Nowak wrote:
>>>
>>> The only low-budget test ideas I have:
>>>
>>> The CD scratching a la Tomas Gustavsson seems the only easily
>>> achievable
>>> solution. But then it is not sure whether the OS does the reading
>>> ret
On 22.12.2009 16:39, Stefan Nowak wrote:
The only low-budget test ideas I have:
The CD scratching a la Tomas Gustavsson seems the only easily
achievable
solution. But then it is not sure whether the OS does the reading
retries
or whether the optical disk drive itself retries reading.
On 2
On 22.12.2009 16:39, Stefan Nowak wrote:
> The only low-budget test ideas I have:
>
> The CD scratching a la Tomas Gustavsson seems the only easily achievable
> solution. But then it is not sure whether the OS does the reading retries
> or whether the optical disk drive itself retries reading.
G
On Tue 22 Dec 2009, Stefan Nowak wrote:
>
> How can one voluntarily "smash" only a particular sector of a hard
> disk drive? Even if you had a test HD for "smashing", you don't know
See (under linux) the manpage for hdparm:
--make-bad-sector
Deliberately create a bad sector (aka. "media er
On Tue, Dec 22, 2009 at 4:18 AM, Tomas Gustavsson wrote:
> Still, I do think that rsync should give up after a long time, but it doesn't.
Yeah, if it gets a read error for a part of a file, it substitutes
zeros for the data and keeps trying to read the file. That could make
it take an eternity f
The only low-budget test ideas I have:
1) Start rsync, and while it is running unmount the source drive,
either by software or simply by physically disconnecting it. But I am
not sure whether this results in the same I/O endless timeout, or
wether this causes different error signaling than
Yeah, I got an Input/Output error when running strace. I don't have the
luxury to smash my harddrive so testing with a CD is my only choice (afaik)
right now. Still, I do think that rsync should give up after a long time,
but it doesn't. So, any advice?
2009/12/22 Paul Slootman >
> On Tue 22 Dec
Did I understand this correctly?
rsync skips a file as soon as it receives an I/O error from the OS?
Then the solution would be to write a script in such a manner:
1) Set OS I/O timeout/attempts to your maximum tolerance.
2) rsync --your --options
3) Set OS I/O timeout/attempts back to the defaul
On Tue 22 Dec 2009, Tomas Gustavsson wrote:
>
> So I took a CD (which I scratched with a needle) and mounted it to the file
> system. There after I started the backup job which went on forever and never
> got completed. It seems that rsync refused to understand that the file it
> tried to copy was
Lately I've working on a backup script that utilize rsync together with
MySQL logging. Everything has been working just fine until now when I needed
to generate some errors for my error handling code.
So I took a CD (which I scratched with a needle) and mounted it to the file
system. There after I
12 matches
Mail list logo
