On Tue, May 28, 2019 at 12:57:18PM +1000, Tom Robinson wrote:
> On Tue, 14 May 2019 at 22:14, Nathan Stratton Treadway
> wrote:
>
> Hi Nathan,
>
> Thanks for you reply and help.
>
> On Mon, May 13, 2019 at 09:59:13 +1000, Tom Robinson wrote:
.
>
> I am getting a new issue now which is anno
out.
> >
> > I can't seem to identify the error when looking in logging. Has anyone a
> few clues as to what to
> > look for?
> >
> > FAILURE DUMP SUMMARY:
> > monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [data
> timeout]
> > m
> clues as to what to
> look for?
>
> FAILURE DUMP SUMMARY:
> monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [data timeout]
> monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [dumper returned
> FAILED]
> monza /data/backup/amanda/vtapes/daily/slot9
gging. Has anyone a few
clues as to what to
look for?
FAILURE DUMP SUMMARY:
monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [data timeout]
monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [dumper returned
FAILED]
monza /data/backup/amanda/vtapes/daily/slot9 lev 0 FAILED [da
meout
waiting for REP]]
clep xerox lev 0 FAILED [data timeout]
clep xerox lev 0 FAILED [dumper returned FAILED]
clep xerox lev 0 FAILED [cannot read header: got 0 bytes instead of 32768]
STRANGE DUMP SUMMARY:
clep oradata lev 0 STRANGE (see below)
STATISTICS:
clep
Date: June 17, 2011
These dumps were to tape CLEP03.
The next tape Amanda expects to use is: CLEP04.
FAILURE DUMP SUMMARY:
clep xerox lev 0 FAILED [too many dumper retry: [request failed: timeout
waiting for REP]]
clep xerox lev 0 FAILED [data timeout]
clep xerox lev 0 FAILED [d
frequency. The server has 150+gig of work area
and this partition less than 35 gig.
The server sees a data timeout and quits, even when I run an amdump
of just this single partition, increasing dtimeout has not helped but
only increased time waiting for failure.
I don't see anything on the s
Thanks to all who have responded so far.
1st, I am aware that what is in debian and ubuntu is not the latest and
greatest. Indeed, it appears to me that what is in ubuntu is just
debian. I did not see any bug reports in the ubuntu archives for
amanda. So, I suspect that there is no real active
On 2009-05-13 00:24, James D. Freels wrote:
I got into debugging mode and discovered why this was happening.
Apparently this upgrade, or a recent change in AMANDA, now forces (or by
error) the data to be compressed with gzip before going from the client
to the server. Even if I specify "compress
On Tue, 12 May 2009 18:43:15 -0400
"Dustin J. Mitchell" wrote:
> On Tue, May 12, 2009 at 6:24 PM, James D. Freels wrote:
> > I got into debugging mode and discovered why this was happening.
> > Apparently this upgrade, or a recent change in AMANDA, now forces
> > (or by error) the data to be com
On Tue, May 12, 2009 at 6:24 PM, James D. Freels wrote:
> I got into debugging mode and discovered why this was happening.
> Apparently this upgrade, or a recent change in AMANDA, now forces (or by
> error) the data to be compressed with gzip before going from the client
> to the server. Even if
Jobst Schmalenbach schreef:
All,
I am replying to my own email cause I fixed it ...
however, I am not sure whether this is a bug!
I tried a lot of things to find the problem ... until I did
a "mount" to display the mounted devices. I just wanted
to see whether a USB HD (which I use for the ODD
though
the workstation is not part of the daily backup routine
jobst
On Wed, Dec 13, 2006 at 11:48:19AM +1100, Jobst Schmalenbach ([EMAIL
PROTECTED]) wrote:
>
> Hi.
>
> All over sudden I get a "data timeout", e.g.:
>
> ...
> ...
>
ou had the same problem I did, but the log files
on the client are a great place to confirm or disprove.
On Wed, Dec 13, 2006 at 11:48:19AM +1100, Jobst Schmalenbach wrote:
>
> Hi.
>
> All over sudden I get a "data timeout", e.g.:
>
> ...
> ...
>
On 2006-12-13 01:48, Jobst Schmalenbach wrote:
>
> All over sudden I get a "data timeout", e.g.:
> adminserver /var lev 0 FAILED [data timeout]
> adminserver /home lev 3 FAILED [data timeout]
[...]
>
> Looking at the "sendbackup..debu
Hi.
All over sudden I get a "data timeout", e.g.:
...
...
adminserver /var lev 0 FAILED [data timeout]
adminserver /home lev 3 FAILED [data timeout]
...
...
I havent changed a thing on the machines involved for
a while (I work on the basic principle "if aint b
ar in my amdump log file.
Yours,
Paul Duncan
Yolus Ltd.
> -Original Message-
> From: Paul Bijnens [mailto:[EMAIL PROTECTED]
> Sent: 31 May 2006 15:53
> To: Paul Duncan
> Cc: amanda-users@amanda.org
> Subject: Re: Data Timeout
>
> On 2006-05-30 10:30, P
On 2006-05-30 10:30, Paul Duncan wrote:
Hello,
One of our filesystems is failing to get backed up and I am interested
in trying to ascertain why. The report entry is:
compaqdev2 /export/home lev 0 FAILED [data timeout]
In the amdump file I see the following suspicious entries. I get a
Hello,
One of our
filesystems is failing to get backed up and I am interested in trying to
ascertain why. The report entry is:
compaqdev2 /export/home lev 0
FAILED [data timeout]
In the amdump file I
see the following suspicious entries. I get a series of "driver-idle:
no-disk
only
DLE exhibiting this behavior.
I have to use anoither tape in the morning and RE-BACKUP this DLE
(Which normally works fine)
It's not really huge.
The error I have in the amanda report is:
FAILURE AND STRANGE DUMP SUMMARY:
sol /disk1/RDBMS_BACKUP lev 0 FAILED [data timeout]
It's
2006/2/9, Matt Hyclak <[EMAIL PROTECTED]>:
> On Thu, Feb 09, 2006 at 02:31:11PM -0500, Guy Dallaire enlightened us:
> > 2006/2/9, Matt Hyclak <[EMAIL PROTECTED]>:
> > >
> > >
> > > Check the setting of your dtimeout value in amanda.conf.
> > >
> > > You might also want to check out
> > > http://www
On Thu, Feb 09, 2006 at 02:31:11PM -0500, Guy Dallaire enlightened us:
> 2006/2/9, Matt Hyclak <[EMAIL PROTECTED]>:
> >
> >
> > Check the setting of your dtimeout value in amanda.conf.
> >
> > You might also want to check out
> > http://www.amanda.org/docs/faq.html#id2551493 if you have a firewall
2006/2/9, Matt Hyclak <[EMAIL PROTECTED]>:
Check the setting of your dtimeout value in amanda.conf.You might also want to check out
http://www.amanda.org/docs/faq.html#id2551493 if you have a firewallconfigured on your CentOS box.
Hum... My dtimeout parameter has already been bumped from 20 minut
t is:
>
> FAILURE AND STRANGE DUMP SUMMARY:
>
> sol /disk1/RDBMS_BACKUP lev 0 FAILED [data timeout]
> It's no really huge.
>
> I'n using amanda 2.4.5 the tape server is centos 4.2 (RHEL 4 Clone)
> and the client with the failing DLE is a sun solaris 9 box.
>
this behavior.
I have to use anoither tape in the morning and RE-BACKUP this DLE
(Which normally works fine)
It's not really huge.
The error I have in the amanda report is:
FAILURE AND STRANGE DUMP SUMMARY:
sol /disk1/RDBMS_BACKUP lev 0 FAILED [data timeout]
It's no really huge.
I'
frank cheong wrote:
Dear Ryan,
Actually not, and I have finally partially solved the problems by
splitting up the disklist to smaller sized folder instead of backing the
whole machine with only a "/". While I still got problem in backing up
one of the /var/log folder of one of the machine an
he amanda setup without problem, my first trial to> backup the etc folder of all host also completed successfully. While I> got the following error when I started to do a full schedule backup test.
>> backupclient1.backupdomain.com:/var 0 driver: [data> timeout] (4:43
error when I started to do a full schedule backup test.
backupclient1.backupdomain.com:/var 0 driver: [data
timeout] (4:43:33)
Any clue what caused this error and where can I further tune up in
order to have this backup completed ?
Frank
--
Ryan Pagquil
Infodyne Inc
I have finished the amanda setup without problem, my first trial to backup the etc folder of all host also completed successfully. While I got the following error when I started to do a full schedule backup test.
backupclient1.backupdomain.com:/var 0 driver: [data timeout] (4:43
t
> > > > and that ended up with a failure due to "data timeout". I didn't even
> > > > know there was a dtimeout value to be specified in amanda.conf. I have
> > > > learnt that it is an idle time measured against the disks in question.
> >
Jon LaBadie wrote:
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to "data timeout". I didn't even
know there was a dtimeout value to be specified in aman
Jon LaBadie wrote:
The documentation says: dtimeout int Default: 1800 seconds. Amount of
idle time per disk on a given client that a dumper running from within
amdump will wait before it fails with a data timeout error.
Glad I said I may be totally wrong :(
Even though
are of "stuck" or
> > "runaway" dump scenarios.
>
> The documentation says: dtimeout int Default: 1800 seconds. Amount of
> idle time per disk on a given client that a dumper running from within
> amdump will wait before it fails with a data timeout er
On Tue, Aug 23, 2005 at 05:04:02PM +0200, Erik P. Olsen enlightened us:
> > On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
> > > I have recently added a set of disks (file systems) to my back-up set
> > > and that ended up with a failure due to "
On Tue, 2005-08-23 at 09:38 -0400, Jon LaBadie wrote:
> On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
> > I have recently added a set of disks (file systems) to my back-up set
> > and that ended up with a failure due to "data timeout". I didn't even
I still have a data timeout error for a DLE in my amanda log this morning.
This is the second time this happens and this DLE is very important
for us. It has to be backed up correctly.
I've looked in the sendbackup.debug files on the client side and there
is no error for this DLE.
I aske
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
> I have recently added a set of disks (file systems) to my back-up set
> and that ended up with a failure due to "data timeout". I didn't even
> know there was a dtimeout value to be specified in amanda.conf.
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to "data timeout". I didn't even
know there was a dtimeout value to be specified in amanda.conf. I have
learnt that it is an idle time measured against the disks in question.
Thank you. That is what I was looking for, a good place to start.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Matt Hyclak
Sent: Thursday, August 04, 2005 12:10 PM
To: Amanda (E-mail)
Subject: Re: data timeout error
On Thu, Aug 04, 2005 at 11:45:21AM
On Thu, Aug 04, 2005 at 11:45:21AM -0400, LaValley, Brian E enlightened us:
> My backup is failing. It worked a couple days ago. It reports a data
> timeout. I have pasted the sendbackup debug file at the end. It warns of
> the index tee cannot write [Broken pipe] What should I be loo
--On Thursday, August 04, 2005 11:45:21 -0400 "LaValley, Brian E" <[EMAIL
PROTECTED]> wrote:
> My backup is failing. It worked a couple days ago. It reports a data
> timeout. I have pasted the sendbackup debug file at the end. It warns of
> the index tee cannot write
My backup is failing. It worked a couple days ago. It reports a data
timeout. I have pasted the sendbackup debug file at the end. It warns of
the index tee cannot write [Broken pipe] What should I be looking into for
this problem? Thank you.
Forwarded Message
From: Quick
Hi,
Hope some one can help with this little problem.
We have amanda backing up various Samba shares and some local Linux
partitions. This has been working reliably for quite some time now. We
are currently using amanda-2.4.4 and samba-2.2.8
Recently amanda is reporting data timeout errors
Hi,
Hope some one can help with this little problem.
We have amanda backing up various Samba shares and some local Linux
partitions. This has been working reliably for quite some time now. We
are currently using amanda-2.4.4 and samba-2.2.8
Recently amanda is reporting data timeout
sage-
From: Christoph Scheeder [mailto:[EMAIL PROTECTED]
Sent: 18 August 2004 12:56
To: Ranveer Attalia
Subject: Re: data timeout - no replies...anyone???
Hi,
If they are working, you can leave them. But i don't trust dump at all,
so i use tar for all my partitions.
So i would sugest switchin
On Wed, 18 Aug 2004 at 5:48pm, Ranveer Attalia wrote
> Interesting
> We are currently using version 2.4.4 p1. Is the Linux ext3 file type
> supported on a later version of Amanda where I can use the dumptype
> nocomp?
(Folks, please trim your messages).
It's not a question of amanda. Aman
: Re: data timeout - no replies...anyone???
Hi,
If they are working, you can leave them. But i don't trust dump at all,
so i use tar for all my partitions.
So i would sugest switching them to tar, especialy as it gives you more
flexibility when it comes to restoring a crashed machine/disk.
I
r
>>>without it and stop complaining if it does not exist.
>>>Christoph
>>
>> At what tarball version did that 'optional' get built in? He may,
>> if a beginner, be trying to use an (spit) rpm. I don't know,
>> either I wasn't pa
ieb:
Hi Christoph
I've found the GNUTAR dumptype and changed the partition which was
failing to backup:
FAILURE AND STRANGE DUMP SUMMARY:
tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
Amanda.conf:
define dumptype root-tar {
global
program "GNUTAR"
comment
a beginner, be trying to use an (spit) rpm. I don't know, either I
wasn't paying enough attention, or he didn't say.
>Ranveer Attalia schrieb:
>> Hi Christoph
>>
>> I've found the GNUTAR dumptype and changed the partition which was
>> failing to back
k with or without it
and stop complaining if it does not exist.
Christoph
Ranveer Attalia schrieb:
Hi Christoph
I've found the GNUTAR dumptype and changed the partition which was
failing to backup:
FAILURE AND STRANGE DUMP SUMMARY:
tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
Am
On Monday 16 August 2004 12:06, Ranveer Attalia wrote:
>Hi Christoph
>
>I've found the GNUTAR dumptype and changed the partition which was
>failing to backup:
>
>FAILURE AND STRANGE DUMP SUMMARY:
> tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
>
>
Hi Christoph
I've found the GNUTAR dumptype and changed the partition which was
failing to backup:
FAILURE AND STRANGE DUMP SUMMARY:
tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
Amanda.conf:
define dumptype root-tar {
global
program "GNUTAR"
On Friday 13 August 2004 05:51, Ranveer Attalia wrote:
>Thanks for getting back to me
>The filesystem version we are using is ext3. Can I run a tar using
>Amanda, so it doesnt interfere with the filesystem versions? How
> would I go about doign that?
>Would a separate config and disklist need to be
heeder; [EMAIL PROTECTED]
Subject: Re: data timeout - no replies...anyone???
On Thursday 12 August 2004 12:08, Ranveer Attalia wrote:
Yes tsslin1 is a linux machine and no there was no finishing line on
sendbackup, but I have another linux machine that is working fine with
the same version of amand
: Re: data timeout - no replies...anyone???
On Thursday 12 August 2004 12:08, Ranveer Attalia wrote:
>Yes tsslin1 is a linux machine and no there was no finishing line on
>sendbackup, but I have another linux machine that is working fine with
>the same version of amanda client on it. Wha
2 4.1 0:00
>34.9
>
>-Original Message-
>From: Christoph Scheeder [mailto:[EMAIL PROTECTED]
>Sent: 12 August 2004 16:57
>To: Ranveer Attalia
>Cc: [EMAIL PROTECTED]
>Subject: Re: data timeout - no replies...anyone???
>
>Hi,
>That is all what your sendbac
h the timeout error and I've checked the sendbackup log file on
> tsslin1 itself. Below is the whole content of the sendbackup log
> file and doesnt seem to give me any errors and appears to be
> dumping fine...
>
>
>FAILURE AND STRANGE DUMP SUMMARY:
> tsslin1
34.9
-Original Message-
From: Christoph Scheeder [mailto:[EMAIL PROTECTED]
Sent: 12 August 2004 16:57
To: Ranveer Attalia
Cc: [EMAIL PROTECTED]
Subject: Re: data timeout - no replies...anyone???
Hi,
That is all what your sendbackup.debug file contains?
no line telling dump reached 100
/opt lev 0 FAILED [data timeout]
tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
sendbackup.20040812055906.debug
sendbackup: debug 1 pid 12551 ruid 33 euid 33: start at Thu Aug 12
05:59:06 2004
/opt/amanda/libexec/sendbackup: version 2.4.4p2
parsed request as: program `DUMP'
--On Thursday, August 12, 2004 09:21:21 +0100 Ranveer Attalia <[EMAIL PROTECTED]>
wrote:
> I'm still having this problem, can anyone help?
>
> -Original Message-
> From: Ranveer Attalia
> Sent: 11 August 2004 11:21
> To: [EMAIL PROTECTED]
> Subject:
f. Below
is the whole content of the sendbackup log file and doesnt seem to give
me any errors and appears to be dumping fine...
FAILURE AND STRANGE DUMP SUMMARY:
tsslin1/opt lev 0 FAILED [data timeout]
tsslin1/export/mansun1_telco lev 0 FAILED [data timeout]
sendbackup.20040
On Thursday 12 August 2004 04:21, Ranveer Attalia wrote:
>I'm still having this problem, can anyone help?
>
>-Original Message-
>From: Ranveer Attalia
>Sent: 11 August 2004 11:21
>To: [EMAIL PROTECTED]
>Subject: data timeout
>
>
>Hi
>
>I recently
problem, can anyone help?
>
> -Original Message-
> From: Ranveer Attalia
> Sent: 11 August 2004 11:21
> To: [EMAIL PROTECTED]
> Subject: data timeout
>
>
> Hi
>
> I recently added two new servers to the daily backup list but now keep
> getting dat
Thanks for the feedback.
I've increased the dtimeout to 10800 so fingers crossed it works
tonight.
- Ranveer
-Original Message-
From: Christoph Scheeder [mailto:[EMAIL PROTECTED]
Sent: 12 August 2004 10:08
To: Ranveer Attalia
Cc: [EMAIL PROTECTED]
Subject: Re: data timeout
you some harm unless you have
hosts beeing offline regularly in your configuration.
Christoph
Ranveer Attalia schrieb:
I'm still having this problem, can anyone help?
-Original Message-
From: Ranveer Attalia
Sent: 11 August 2004 11:21
To: [EMAIL PROTECTED]
Subject: data timeout
On Thu, 12 Aug 2004, Ranveer Attalia wrote:
> I'm still having this problem, can anyone help?
Try to increase dtimeout even more.
> -Original Message-
> From: Ranveer Attalia
> Sent: 11 August 2004 11:21
> To: [EMAIL PROTECTED]
> Subject: data timeout
>
>
I'm still having this problem, can anyone help?
-Original Message-
From: Ranveer Attalia
Sent: 11 August 2004 11:21
To: [EMAIL PROTECTED]
Subject: data timeout
Hi
I recently added two new servers to the daily backup list but now keep
getting data timeout errors for them.
I
Hi
I recently added two new servers to the daily backup list but now keep
getting data timeout errors for them.
I have already increased my dtimeout parameter in the amanda.conf file
to 7200 before I added the new servers. Can anyone tell me if there is a
more reasonable size I can increase
this yet?
>
> I'd suggest raising it a massive amount and see if the dump
> completes at some point.
>
> You can monitor that things are still running with commands
> like top, ps, prstat, ... depending on your OS and available tools.
Amstatus is also a good way to check on
On Mon, May 24, 2004 at 10:48:17AM -0700, Kris Vassallo wrote:
> In response to my own message, I was reading around a bit more and the
> broken pipe could be many things but usually means that the data isn't
> being dumped fast enough and the server gives up on the client (in my
> case the same ma
e answer to why.
>Here's whats going on... AMANDA sends me an email with the following
>information:
>
>These dumps were to tape DailySet118.
>The next tape Amanda expects to use is: a new tape.
>
>FAILURE AND STRANGE DUMP SUMMARY:
> bda2.berke //illustrator/BDA_Manual
use is: a new tape.
>
>FAILURE AND STRANGE DUMP SUMMARY:
> bda2.berke //illustrator/BDA_Manual lev 1 STRANGE
> venus.berk /home lev 1 FAILED [data timeout]
>*SNIP*
>/-- venus.berk /home lev 1 FAILED [data timeout]
Please note it says "data timeout" here.
>sendbackup: s
>These dumps were to tape DailySet118.
>The next tape Amanda expects to use is: a new tape.
>
>FAILURE AND STRANGE DUMP SUMMARY:
> bda2.berke //illustrator/BDA_Manual lev 1 STRANGE
> venus.berk /home lev 1 FAILED [data timeout]
>*SNIP*
>/-- venus.berk /home lev 1 FAILED [data
with the following information:
KV> These dumps were to tape DailySet118.
KV> The next tape Amanda expects to use is: a new tape.
KV> FAILURE AND STRANGE DUMP SUMMARY:
KV> bda2.berke //illustrator/BDA_Manual lev 1 STRANGE
KV> venus.berk /home lev 1 FAILED [data timeout]
KV> *SNIP*
is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
bda2.berke //illustrator/BDA_Manual lev 1 STRANGE
venus.berk /home lev 1 FAILED [data timeout]
*SNIP*
/-- venus.berk /home lev 1 FAILED [data timeout]
sendbackup: start [venus.berkeley-da.com:/home level 1]
sendbackup: info BACKUP=/bin/tar
sendba
>
>
> I've had this happen a couple of times, if you can afford the extra
> tape, you can remove the compression, or have the server do the
> compression instead of the client.
>
They are 40GB tapes for around 5-10GB backups, so I could. I ill look at teh
compression issue.
Gavin.
>
> Are you using dump or tar for that fs? dump has some issues
> with the 2.4
> kernel that often lead to data timeouts...
>
I think I have it set to comp-root-tar.
Gavin.
On Mon, 15 Mar 2004 at 10:35am, Gavin Henry wrote
> > Gavin Henry wrote:
> > > Is there a way to increase the wait time for a particular
> > partition/directory?
> >
> > It's a global parameter, not particular to some partition.
> > In amanda.conf:
> >
> > dtimeout 3600
> >
> > or somethin
>
> Gavin Henry wrote:
> > Is there a way to increase the wait time for a particular
> partition/directory?
>
> It's a global parameter, not particular to some partition.
> In amanda.conf:
>
> dtimeout 3600
>
> or something like that. You need amanda 2.4.3 or later for it.
>
OK, damn, I
[data timeout]
All other partitions on the server are fine.
Is there a way to increase the wait time for a particular partition/directory?
Gavin.
**
Kind Regards,
Gavin Henry.
BEng (Hons) MIEE
Engineer
Invsat Ltd
On 13 Jun 2003 at 9:25am, Eric Sproul wrote
> No, in fact the host is running the 2.4.7-10smp kernel that was
> originally installed. I'm anticipating replacing this machine with new
> hardware sometime this year, so I think I'll just switch to tar until I
> can rip it out.
There have been a num
On Fri, 2003-06-13 at 09:20, Joshua Baker-LePain wrote:
> Is the host fully updated (especially glibc and the kernel)? Dump on 2.4
> series kernels has always been a contentious issue. After moving to 2.4
> and seeing lots of timeouts, I converted all my dumptypes to using tar.
> No problems
On 13 Jun 2003 at 9:11am, Eric Sproul wrote
> I have recently seen a couple occurrences of a "data timeout" on a
> particular DLE that I cannot figure out. The host is running RH7.2,
> serving GNU MailMan lists. It has 512MB of RAM and 2 20G IDE disks
> running software-RA
Hi all,
I have recently seen a couple occurrences of a "data timeout" on a
particular DLE that I cannot figure out. The host is running RH7.2,
serving GNU MailMan lists. It has 512MB of RAM and 2 20G IDE disks
running software-RAID1.
The device giving me trouble is /dev/md6, an ext
pass without a reply from tar.
Thanks again,
Dick
> On Sat, Jun 07, 2003 at 03:22:33AM -, [EMAIL PROTECTED] wrote:
> > Since I have converted from samba to cygwin clients on our windows
> > machines, I occasionally get the error below:
> >
> > andorian.americom.com
On Sat, Jun 07, 2003 at 03:22:33AM -, [EMAIL PROTECTED] wrote:
> Since I have converted from samba to cygwin clients on our windows
> machines, I occasionally get the error below:
>
> andorian.americom.com:/cygdrive/c 0 driver: [data timeout] (20:42:43)
>
> It happens on e
Since I have converted from samba to cygwin clients on our windows
machines, I occasionally get the error below:
andorian.americom.com:/cygdrive/c 0 driver: [data timeout] (20:42:43)
It happens on each of the windows machines with no particular order to
it. I am wondering if there is a timeout
> > I might be making progress; I'm not sure.
> >
>[ snip ]
> >
> > So... Why does the server close (FIN) all three connections only 1 second
> > after opening them? I can find no messages in the server logs as to why
> > this might have happened.
>
> Don't know my networking and tcpdump, so
is has worked! However...
When the client runs, the server gets the following:
/-- watertown. /home/watertown lev 1 FAILED [data timeout]
sendbackup: start [watertown.ott.precidia.com:/home/watertown level 1]
sendbackup: info BACKUP=/usr/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -d
ession because we
> > > > > got a new tape changer. Perhaps that's the cause of the
> > > > > problems.
> >
> > Sounds unlikely. You don't get data timeout from a tape drive.
>
> What I meant was that because we switched to a new tap
Then it proceeds to the dumps. It's dumped 3 file systems successfully
so far, and 1 has failed (data timeout). The one that failed, the dump
process is still sitting out there, and a new one was created for
another dump.
> This doesn't add up, you're moving about 2.2 megs/
27;s the cause of the
> > > > problems.
>
> Sounds unlikely. You don't get data timeout from a tape drive.
What I meant was that because we switched to a new tape changer, we
decided to turn on hardware compression and turn off software
compression. Perhaps the change of
On Wed, Aug 28, 2002 at 03:44:36PM -0400, Gene Heskett wrote:
> On Wednesday 28 August 2002 15:13, Amy Tanner wrote:
> >On Wed, Aug 28, 2002 at 02:30:41PM -0400, Gene Heskett
> >etimeout 300
>
> Which looks like enough, but note on down the page where it
> indicates it took 7 minutes, not 5.
C
On Wed, Aug 28, 2002 at 02:30:41PM -0400, Gene Heskett wrote:
> 3600 certainly does seem like enough, thats ten hours!
Nope. 1 hour. I've seen seen data timeout failures on incrementals
for file systems with very large numbers of small files with
dtimeout=1800, FWIW.
Amy asked:
> &
etimeout value? Thats the amount of time allowed
>> forf the estimate phase's report to come back.
>
>etimeout 300
Which looks like enough, but note on down the page where it
indicates it took 7 minutes, not 5.
>It looks like the estimate phase completes though:
>
&
On Wednesday 28 August 2002 14:30, Gene Heskett wrote:
>On Wednesday 28 August 2002 13:20, Amy Tanner wrote:
>>On Wed, Aug 28, 2002 at 01:06:37PM -0400, Gene Heskett
>
>([EMAIL PROTECTED]) wrote:
>>> It rather sounds like you need to allow more time for the
>>> process to run. Thats configurable
It looks like the estimate phase completes though:
/-- delphi.ahp /u04 lev 0 FAILED [data timeout]
sendbackup: start [delphi.ahpcrc.org:/u04 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Tue Aug
On Wednesday 28 August 2002 13:20, Amy Tanner wrote:
>On Wed, Aug 28, 2002 at 01:06:37PM -0400, Gene Heskett
([EMAIL PROTECTED]) wrote:
>> It rather sounds like you need to allow more time for the
>> process to run. Thats configurable with a couple of variables
>> in your amanda.conf file, along
Using gtar might help also.
On Wed, 2002-08-28 at 12:20, Amy Tanner wrote:
> On Wed, Aug 28, 2002 at 01:06:37PM -0400, Gene Heskett ([EMAIL PROTECTED])
>wrote:
> > It rather sounds like you need to allow more time for the process to
> > run. Thats configurable with a couple of variables in y
1 - 100 of 153 matches
Mail list logo
