Our setup: - AMANDA server: Debian 'Stable' release, 2.6.1p2-3 direct from Debian packages;
- AMANDA clients: various, Debian 'Stable' with same version as above. We upgraded from Debian 'oldstable' to 'stable' in the past few months and since upgrading the client, we occasionally see the following on one of our servers, named 'athena' relating to the /home volume which is currently approximately 1.7TB in size. For example from this morning: FAILURE DUMP SUMMARY: athena /home lev 0 FAILED "/usr/lib/amanda/runtar exited with status 1: see /var/log/amanda/client/Daily/sendsize.20111118234504.debug" The pertinent part of /var/log/amanda/client/Daily/sendsize.20111118234504.debug is: ------------------------------------------------------------------------ 1321659908.212265: sendsize: waiting for any estimate child: 1 running 1321659908.212332: sendsize: calculating for amname /home, dirname /home, spindle -1 GNUTAR 1321659908.212399: sendsize: getting size via gnutar for /home level 0 1321659908.213588: sendsize: pipespawnv: stdoutfd is 3 1321659908.213715: sendsize: Spawning "/usr/lib/amanda/runtar runtar Daily /bin/tar --create --file /dev/null --numeric-owner --directory /home --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/athena_home_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._home.20111118234508.exclude ." in pipeline 1321660065.551101: sendsize: Total bytes written: 1831488286720 (1.7TiB, 11GiB/s) 1321660065.551698: sendsize: ..... 1321660065.551733: sendsize: estimate time for /home level 0: 157.338 1321660065.551742: sendsize: estimate size for /home level 0: 1788562780 KB 1321660065.551754: sendsize: waiting for runtar "/home" child 1321660065.570903: sendsize: after runtar /home wait 1321660065.592913: sendsize: getting size via gnutar for /home level 4 1321660065.701616: sendsize: pipespawnv: stdoutfd is 3 1321660065.711458: sendsize: Spawning "/usr/lib/amanda/runtar runtar Daily /bin/tar --create --file /dev/null --numeric-owner --directory /home --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/athena_home_4.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._home.20111118234745.exclude ." in pipeline 1321660183.361325: sendsize: Total bytes written: 8443156480 (7.9GiB, 69MiB/s) 1321660183.361910: sendsize: ..... 1321660183.361935: sendsize: estimate time for /home level 4: 117.660 1321660183.361944: sendsize: estimate size for /home level 4: 8245270 KB 1321660183.361952: sendsize: waiting for runtar "/home" child 1321660183.387790: sendsize: after runtar /home wait 1321660183.409511: sendsize: getting size via gnutar for /home level 5 1321660183.513086: sendsize: pipespawnv: stdoutfd is 3 1321660183.513274: sendsize: Spawning "/usr/lib/amanda/runtar runtar Daily /bin/tar --create --file /dev/null --numeric-owner --directory /home --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/athena_home_5.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._home.20111118234943.exclude ." in pipeline 1321660292.407967: sendsize: /bin/tar: ./heather/CEU_Work/csrc/bbquaire/mwlv_cron/nutauto.chk: File removed before we read it 1321660298.633046: sendsize: Total bytes written: 4815687680 (4.5GiB, 41MiB/s) 1321660298.633493: sendsize: ..... 1321660298.633518: sendsize: estimate time for /home level 5: 115.120 1321660298.633526: sendsize: estimate size for /home level 5: 4702820 KB 1321660298.633533: sendsize: waiting for runtar "/home" child 1321660298.659697: sendsize: after runtar /home wait 1321660298.681181: sendsize: errmsg is /usr/lib/amanda/runtar exited with status 1: see /var/log/amanda/client/Daily/sendsize.20111118234504.debug 1321660298.681237: sendsize: done with amname /home dirname /home spindle -1 ------------------------------------------------------------------------ I note that there were changes on the filesystem during the backup process: this is normal (cron jobs etc.) and has caused nothing other than a 'STRANGE' note in the report previously. I also note that the error relates to a level 5 backup, but that a level 0 backup was actually carried out, apparently successfully: ------------------------------------------------------------------------ athena /home 0 1788562460 532736530 29.8 746:27 11894.8 137:06 64766.4 ------------------------------------------------------------------------ I believe this is the appropriate runtar.*.debug corresponding to above, based on the timestamps: ------------------------------------------------------------------------ 1321660183.516316: runtar: pid 2400 ruid 34 euid 0 version 2.6.1p2: start at Fri Nov 18 23:49:43 2011 1321660183.516378: runtar: version 2.6.1p2 1321660183.519739: runtar: /bin/tar version: tar (GNU tar) 1.23 1321660183.519872: runtar: config: Daily 1321660183.520622: runtar: pid 2400 ruid 0 euid 0 version 2.6.1p2: rename at Fri Nov 18 23:49:43 2011 1321660183.520836: runtar: running: /bin/tar --create --file /dev/null --numeric-owner --directory /home --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/athena_home_5.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._home.20111118234943.exclude . 1321660183.520853: runtar: pid 2400 finish time Fri Nov 18 23:49:43 2011 ------------------------------------------------------------------------ No obvious error recorded there. Can someone explain why the above situation results in a hard error? Am happy to supply further log extracts if required. I appreciate that AMANDA development is now concentrated on the 3.x series and that I may receive some suggestions to upgrade: however, I prefer to use distribution-supplied packages where possible. And, in our experience, this has always worked very reliably in the past. Thanks, Dave. -- Dave Ewart da...@ceu.ox.ac.uk Computing Manager, Cancer Epidemiology Unit University of Oxford / Cancer Research UK N 51.7516, W 1.2152
signature.asc
Description: Digital signature
