Amanda-Users

Mystery holding disk issue

2003-01-28 12:56:41
Subject: Mystery holding disk issue
From: John Oliver <joliver AT john-oliver DOT net>
To: amanda-users AT amanda DOT org
Date: Tue, 28 Jan 2003 09:16:34 -0800
Got this:

These dumps were to tape Indyme007.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Indyme006.

FAILURE AND STRANGE DUMP SUMMARY:
  cm         /dev/hda2 lev 0 FAILED [out of tape]
  cm         /dev/hda2 lev 0 FAILED [dump to tape failed]
  devdist    /dev/hda2 lev 1 FAILED [no more holding disk space]
  qaweb      /dev/hdc2 lev 1 FAILED [no more holding disk space]
  qadb       /dev/hda2 lev 1 FAILED [no more holding disk space]


So, I ran amflush, and received this:

*** A TAPE ERROR OCCURRED: [rewinding tape: Input/output error].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: Indyme006.


STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:00
Run Time (hrs:min)         0:01
Dump Time (hrs:min)        0:00       0:00       0:00
Output Size (meg)           0.0        0.0        0.0
Original Size (meg)         0.0        0.0        0.0
Avg Compressed Size (%)     --         --         -- 
Filesystems Dumped            0          0          0
Avg Dump Rate (k/s)         --         --         -- 

Tape Time (hrs:min)        0:00       0:00       0:00
Tape Size (meg)             0.0        0.0        0.0
Tape Used (%)               0.0        0.0        0.0
Filesystems Taped             0          0          0
Avg Tp Write Rate (k/s)     --         --         -- 

DUMP SUMMARY:
                                     DUMPER STATS            TAPER STATS 
HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS
KB/s
-------------------------- ---------------------------------
------------
backup       /dev/hda1     NO FILE TO FLUSH
-----------------------------
cm           /dev/hda1     NO FILE TO FLUSH
-----------------------------
cm           /dev/hda2     NO FILE TO FLUSH
-----------------------------
cm           /dev/hda3     NO FILE TO FLUSH
-----------------------------
cm           /dev/hda5     NO FILE TO FLUSH
-----------------------------
cm           /dev/hda7     NO FILE TO FLUSH
-----------------------------
devcoll      /dev/hdc2     NO FILE TO FLUSH
-----------------------------
devdb        /dev/hda2     NO FILE TO FLUSH
-----------------------------
devdist      /dev/hda2     NO FILE TO FLUSH
-----------------------------
devweb       /dev/hda2     NO FILE TO FLUSH
-----------------------------
qaall        /dev/hdc2     NO FILE TO FLUSH
-----------------------------
qacoll       /dev/hda2     NO FILE TO FLUSH
-----------------------------
qadb         /dev/hda2     NO FILE TO FLUSH
-----------------------------
qadist       /dev/hda2     NO FILE TO FLUSH
-----------------------------
qaweb        /dev/hdc2     NO FILE TO FLUSH
-----------------------------


So, which is it?  Is there something that needs to be flushed or not???

-- 
John Oliver, CCNA                            http://www.john-oliver.net/
Linux/UNIX/network consulting         http://www.john-oliver.net/resume/
***               sendmail, Apache, ftp, DNS, spam filtering         ***
****                Colocation, T1s, web/email/ftp hosting          ****

<Prev in Thread] Current Thread [Next in Thread>