Amanda-Users

dump done, wait for writing - endless

2004-09-23 15:43:30
Subject: dump done, wait for writing - endless
From: Kai Zimmer <kai AT zimmer DOT net>
To: amanda-users AT amanda DOT org
Date: Thu, 23 Sep 2004 21:38:10 +0200
Hello,

i'm using Amanda 2.4.4p2 on linux for some time now without problems. But the last two backups didn't suceed.

I'm backing up about 850 Gb from 8 clients (11 filesets). 8 of my filesets were processed correctly, but now it stopped with "dump done, wait for writing to tape". I'm waiting for ~12 hrs now, last time (when i was on holidays) it was in this state for ~3 weeks...

The tapechanger has loaded the next tape properly, but the (tar-made)dump isn't flushed to tape. There are several amanda processes running, but only the driver seems to consume cpu-time.

The only hint i could find is that the amdump logfile complains not to have enough diskspace - although i have 300 Gb diskspace reserved for amanda (it was empty before the backup, and none of the filesets has more than 180 Gb).

Any ideas?
thanks,
Kai


----------------------------------------------------------------------
kirk:~/amanda # amstatus full
Using /home/amanda/full/amdump from Son Sep 19 10:02:25 CEST 2004

before:/home               0 53228380k finished (1+23:38:15)
...
kira:/home/konvert 0133949120k dump done (3+15:14:23), wait for writing to tape
kirk:/home/clip            0110246800k wait for dumping

SUMMARY          part      real  estimated
                           size       size
partition       :  11
estimated       :  11            845683550k
flush           :   0         0k
failed          :   0                    0k           (  0.00%)
wait for dumping:   2            220263790k           ( 26.05%)
dumping to tape :   0                    0k           (  0.00%)
dumping         :   0         0k         0k (  0.00%) (  0.00%)
dumped          :   9 625445850k 625419760k (100.00%) ( 73.96%)
wait for writing:   1 133949120k 133949120k (100.00%) ( 15.84%)
wait to flush   :   0         0k         0k (100.00%) (  0.00%)
writing to tape :   0         0k         0k (  0.00%) (  0.00%)
failed to tape  :   0         0k         0k (  0.00%) (  0.00%)
taped           :   8 491496730k 491470640k (100.01%) ( 58.12%)
  tape 1        :   7 311178390k 311152300k (147.01%) volume002
  tape 2        :   1 180318340k 180318340k ( 85.19%) volume003
16 dumpers idle : no-diskspace
taper writing, tapeq: 1
network free kps:   2252800
holding space   :  47417296k ( 13.11%)
 dumper0 busy   : 2+14:47:27  ( 88.21%)
...
 dumper5 busy   :  0:59:17  (  1.39%)
   taper busy   : 2+4:12:17  ( 73.34%)
0 dumpers busy : 2:57:34 ( 4.16%) no-diskspace: 2:57:34 (100.00%)
...
6 dumpers busy : 0:23:52 ( 0.56%) no-diskspace: 0:23:52 (100.00%)
----------------------------------------------------------------------

kirk:/home/amanda/full # tail log
SUCCESS dumper kira /home/prepare_rehbein 20040919 0 [sec 165746.816 kb 180318340 kps 1087.9 orig-kb 180318340] SUCCESS taper kira /home 20040919 0 [sec 24081.353 kb 83670280 kps 3474.5 {wr: writers 2614698 rdwait 15926.413 wrwait 7690.743 filemark 46.950}] INFO taper tape volume002 kb 408802400 fm 8 writing file: No space left on device
START taper datestamp 20040919 label volume003 tape 1
INFO taper retrying kira:/home/prepare_rehbein.0 on new tape: [writing file: No space left on device] SUCCESS dumper kira /home/konvert 20040919 0 [sec 60299.867 kb 133949120 kps 2221.4 orig-kb 133949120] SUCCESS taper kira /home/prepare_rehbein 20040919 0 [sec 45034.168 kb 180318340 kps 4004.0 {wr: writers 5634950 rdwait 27227.209 wrwait 17078.716 filemark 3.852}]

<Prev in Thread] Current Thread [Next in Thread>
  • dump done, wait for writing - endless, Kai Zimmer <=