This one time, at band camp, Jon LaBadie wrote:
>On Thu, Aug 18, 2005 at 10:16:48AM +1000, Jamie Wilkinson wrote:
>>
>> Another data point though; this backup today started at 1:30am (it's now
>> 10:15am) and is only 35% through -- about 20GiB. This is pretty abnormal
>> (well, compared back to w
On Thu, Aug 18, 2005 at 10:16:48AM +1000, Jamie Wilkinson wrote:
>
> Another data point though; this backup today started at 1:30am (it's now
> 10:15am) and is only 35% through -- about 20GiB. This is pretty abnormal
> (well, compared back to when it used to run -- it would on a bad day be
> fini
This one time, at band camp, Jon LaBadie wrote:
>As I noted, I was uncertain of the details, someone understanding more
>about the networking aspects can comment more. But just for clarification
>of the way I worded that:
>
>- I did not say anything about the backup data stream over udp
>- Your lo
This one time, at band camp, Scott R. Burns wrote:
>Can the version of GNU tar you are using handle single archives of this size
>? There were some older versions that used signed long internals that
>overflowed on me in the past and caused problems.
It's 1.13.25 from RHEL 3. I havne't seen anyth
On Wed, Aug 17, 2005 at 03:05:01PM +1000, Jamie Wilkinson wrote:
> This one time, at band camp, Jon LaBadie wrote:
> >Search back over the list archives for details that I don't remember.
>
> Thanks :)
>
> >I think some have had this symptom when there was some sort of network
> >timeout setting
This one time, at band camp, Jon LaBadie wrote:
>Search back over the list archives for details that I don't remember.
Thanks :)
>I think some have had this symptom when there was some sort of network
>timeout setting that affected the index stream. Not certain, but I
>think it was a UDP setting
On Wed, Aug 17, 2005 at 12:35:46PM +1000, Jamie Wilkinson wrote:
> I have a very large DLE, approaching 100GB, on my fileserver. The backup
> server is running 2.4.5, and the fileserver is running 2.4.5b1.
>
> The dump on this DLE is returning the following error:
>
> bulkhead.b /data/home lev
Subject: odd dump timeout symptoms
I have a very large DLE, approaching 100GB, on my fileserver. The backup
server is running 2.4.5, and the fileserver is running 2.4.5b1.
The dump on this DLE is returning the following error:
bulkhead.b /data/home lev 0 FAILED [data read: Connection reset by
I have a very large DLE, approaching 100GB, on my fileserver. The backup
server is running 2.4.5, and the fileserver is running 2.4.5b1.
The dump on this DLE is returning the following error:
bulkhead.b /data/home lev 0 FAILED [data read: Connection reset by peer]
in the summary, which looks
