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 0 FAILED [data read: Connection reset by peer] > > in the summary, which looks like this in the sendbackup log on this client: > > sendbackup: time 10.050: spawning /usr/lib/amanda/runtar in pipeline > sendbackup: argument list: gtar --create --file - --directory /home > --one-file-system --listed-incremental > /var/lib/amanda/gnutar-lists/bulkhead.backup_data_home_0.new --sparse > --ignore-failed-read --totals --exclude-from > /var/log/amanda/sendbackup._data_home.20050817013729.exclude . > sendbackup-gnutar: time 10.051: /usr/lib/amanda/runtar: pid 6101 > sendbackup: time 10.055: started index creator: "/bin/tar -tf - 2>/dev/null | > sed -e 's/^\.//'" > sendbackup: time 22182.305: index tee cannot write [Broken pipe] > sendbackup: time 22182.305: 126: strange(?): > sendbackup: time 22182.326: pid 6099 finish time Wed Aug 17 07:47:01 2005 > sendbackup: time 22182.327: 126: strange(?): gzip: stdout: Connection timed > out > sendbackup: time 22182.328: 126: strange(?): sendbackup: index tee cannot > write > [Broken pipe]
Search back over the list archives for details that I don't remember. 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 for how long a connection could be open. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)