Erik,
2.5.5 rsync crashes and burns my hard disk, you are indeed lucky to get a
segmentation fault.
When I reported flakiness I was told it was my hardware. I upgraded my
hardware - no difference.
Then I was told to change my 2.4.x kernel. Why? it runs everything else,
and has reliably for over
till use rsync a lot, but as just another tool, like tar, cp, rsh,
>whatever.
>
>Good luck.
>
>Tim Conway
>[EMAIL PROTECTED]
>303.682.4917 office, 303.921.0301 cell
>Philips Semiconductor - Longmont TC
>1880 Industrial Circle, Suite D
>Longmont, CO 80501
>Available v
Tim,
I just got the hung rsync window to respond to a Control-C and it put out
the following text (including a few of those make files that were just
before it hung..
make_file(4,var/adm/fillup-templates/i4l_default.templ)
make_file(4,var/adm/fillup-templates/i4l_hardware.templ)
make_file(4,var/a
-then hangs-
Any ideas?
Last time I was told to upgrade my hardware and OS.
I run a solid, scrupulously updated, SuSE 7.3 system on reliable P-II/400
hardware
..Trevor Marshall...
At 10:36 AM 9/17/2002 -0600, you wrote:
>Certainly, you should upgrade your rsync. 2.4.6 had m
>Is there more than one rsync running? In 2.5.4 a failure in another rsync
>process could kill your rsync. I haven't studied the code recently, but I
>don't think there are any calls to fork() after it has started transfering
>files.
I recall
bash$ ps -aux
showed 2 rsync processes, maybe thr
Paul,
Was running 2.5.4, Compiled and upgraded to 2.5.5
No crash this time, but it again failed on a (possibly open) logfile. There
might be a hint there...
Ran it again - no crash, same error...
Verbose output was:
Trevors:~ # ./make_snapshot.sh
umount: /dev/hdc1: not mounted
building file list
Peter,
One other thing.
The first two times it crashed I erased the file tree created by rsync so
that the snaphot started from scratch again.
Each of these two times it got to exactly the same file:
usr/lib/locale/es_CO/LC_COLLATE
when it crashed.
That was when I stopped rebuidling and re-c
At 09:36 PM 9/8/2002 -0400, you wrote:
>I agree often if the kernel crashes, though the kernel should be well
>protected enough to only crash the application process, and not damage
>itself, often the kernel flaw is stimulated by an errant or out of range
>value in it's input which woudl cause
Jw,
Respectfully,
My experience is to shy away from any piece of software which the
developers feel is inviolate
Although often the hardware and kernel certainly could be at fault it is
wrong to assume they are, and such a response usually indicates that I am
wasting my time reporting this proble
Dear JW,
I spent hours checking and upgrading my hardware. There is nothing wrong
with it. It is a 'mature' Pentium-II 400MHz system that has been running my
servers WITHOUT ANY CRASHES for nearly 2 years now 24/7
Listen to me: "The crashes are dues to rsync"
There is an IDENTICAL report from a
On Sun, Sep 08, 2002 at 01:08:48PM -0700, Trevor Marshall wrote:
> I have been trying to implement Mike's tutorial on backup with rsync, but
> my server has kept crashing in the middle of the rsync transfer.
>
> I am backing up /dev/hda1 to /dev/hdc1 on a SuSe v 7.3 i38
I have been trying to implement Mike's tutorial on backup with rsync, but
my server has kept crashing in the middle of the rsync transfer.
I am backing up /dev/hda1 to /dev/hdc1 on a SuSe v 7.3 i386 box
Server crashed 8 times. 16 fsck and 8 reboots later I finally got an error
message and a
12 matches
Mail list logo
