Re: Failing on relatively large partition

2001-02-09 Thread Chris Hobbs
Success! Increased dtimeout to 7200 and I now have a good backup of /home. Thanks a ton for all the help. Alexandre Oliva wrote: > > On Feb 8, 2001, Chris Hobbs <[EMAIL PROTECTED]> wrote: > > > If this is the case, then the culprit appears to be the first gtar, as > > it has taken forever to s

Re: Failing on relatively large partition

2001-02-08 Thread Alexandre Oliva
On Feb 8, 2001, Chris Hobbs <[EMAIL PROTECTED]> wrote: > If this is the case, then the culprit appears to be the first gtar, as > it has taken forever to start piping data into gzip That's indeed the way GNU tar works. > If these assumptions are correct, any suggestions? Increase dtimeout (ne

Re: Failing on relatively large partition

2001-02-08 Thread Chris Hobbs
"John R. Jackson" wrote: > * Run sendbackup by hand as the Amanda user like this: > > /path/to/sendbackup -t < /the/file > /tmp/index.out Two hours into this now and it seems to be running somewhat correctly - strace (no truss here) shows and has shown a lot of file activity on the firs

Re: Failing on relatively large partition

2001-02-08 Thread John R. Jackson
>1.13.17, which I understand is acceptable, correct? That's my understanding. I think 1.13.19 has some performance improvements and an obscure bug fix, but for what you're seeing I don't think they apply (I think you're seeing a hang, not a performance problem). >Should have been more clear her

Re: Failing on relatively large partition

2001-02-08 Thread John R. Jackson
>His log also shows >started index creator: "/usr/bin/gtar -tf - 2>/dev/null |sed -e 's/ >^\.//'" >index tee cannot write [Broken pipe] > >Might this be the reason ? No, that's a symptom. It says the other side of the connection (dumper on the server side) went away, which we knew. >Chris,

Re: Failing on relatively large partition

2001-02-08 Thread John R. Jackson
First, quickly grab the amandad*debug file for this run. With luck, it will still be for the backup of /home. It has a command we'll use shortly. >So, sendbackup for /home begins at 23:08, amanda quits and sends out the >MAIL REPORT 30 minutes later at 23:38 with the "[data timeout]" error, Wh

Re: Failing on relatively large partition

2001-02-08 Thread Chris Hobbs
Some more info. The backup of /home on failed again last night, but I notice the following: >From sendbackup.debug: 1) sendbackup: debug 1 pid 25115 ruid 40582 euid 40582 start time Wed Feb 7 23:08: 22 2001 2) The AMANDA MAIL REPORT was sent at 23:38. 3) [root@svhsfiles /tmp/amanda]# ls -l se

Re: Failing on relatively large partition

2001-02-08 Thread Chris Hobbs
Thanks for the quick reply! "John R. Jackson" wrote: > What version of tar are you using? 1.13.17, which I understand is acceptable, correct? > What kind of connection exists between client and server? Any firewalls > or that kind of thing? Should have been more clear here - svhsfiles is th

Re: Failing on relatively large partition

2001-02-08 Thread Gerhard den Hollander
* John R. Jackson <[EMAIL PROTECTED]> (Thu, Feb 08, 2001 at 12:43:32AM -0500) >> svhsfiles /home lev 0 FAILED [data timeout] > This says dumper on the server last heard from sendbackup on the client > 30 minutes ago and gave up waiting. This (probably) has nothing to do > with your tapes or dr

Re: Failing on relatively large partition

2001-02-07 Thread John R. Jackson
> svhsfiles /home lev 0 FAILED [data timeout] This says dumper on the server last heard from sendbackup on the client 30 minutes ago and gave up waiting. This (probably) has nothing to do with your tapes or drive and possibly nothing to do with the size of the file system being backed up unles

Failing on relatively large partition

2001-02-07 Thread Chris Hobbs
Problem: Amanda has consistently failed backing up /home on svhsfiles for the last several weeks, originally with Amanda 2.4.1, now with 2.4.2. The partition has approximately 17GB of data on it. The tape is a DDS3 12/24GB drive. The other partitions backing up have used from 850M-3G of space on t