Recompiling with the --without-ipv6 option didn't change anything unfortunately, and I noticed in the report email that all of the file systems targetted for backup are being reported as:
FAILURE AND STRANGE DUMP SUMMARY: jedi /dev/dsk/c0t0d0s6 RESULTS MISSING jedi /dev/dsk/c0t0d0s3 RESULTS MISSING jedi /dev/dsk/c0t0d0s7 RESULTS MISSING jedi /dev/dsk/c0t1d0s7 RESULTS MISSING lios /dev/dsk/c3t1d0s0 RESULTS MISSING lios /dev/dsk/c3t1d0s6 RESULTS MISSING lios /dev/dsk/c3t1d0s3 RESULTS MISSING lios /dev/dsk/c3t2d0s7 RESULTS MISSING yoda /dev/dsk/c0t0d0s6 RESULTS MISSING yoda /dev/dsk/c0t0d0s3 RESULTS MISSING yoda /dev/dsk/c0t1d0s7 RESULTS MISSING yoda /dev/dsk/c2t2d0s3 RESULTS MISSING yoda /dev/dsk/c3t1d0s4 RESULTS MISSING driver: FATAL infofile update failed (yoda,'/dev/dsk/c0t0d0s0') Could this still be network-related? I'm thinking not. According to the report email, it seems to have actually written data to tape for two file systems but that might be a misnomer. The amdump log/debug file is at http://jedi.apana.org.au/~amanda/amdump.01102007<http://jedi.apana.org.au/%7Eamanda/amdump.01102007>for anyone interested to view the log. I'd appreciate any suggestions you can provide. Craig. -- Craig Dewick ([EMAIL PROTECTED]). http://lios.apana.org.au/~craig RailZone Australia: http://www.railzone.org ([EMAIL PROTECTED]) The SunShack: http://www.sunshack.org ([EMAIL PROTECTED]) ClassicSaab: http://www.classicsaab.net ([EMAIL PROTECTED])
