Amanda-Users

Re: amstatus: no estimate and disk was stranded on waitq

2007-07-24 02:05:10
Subject: Re: amstatus: no estimate and disk was stranded on waitq
From: fedora <zuki AT abamon DOT com>
To: amanda-users AT amanda DOT org
Date: Mon, 23 Jul 2007 23:00:05 -0700 (PDT)
Spam detection software, running on the system "sapphire.omniscient.com", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
postmaster for details.

Content preview:  Hello, Yesterday 23 July 2007 the backup still in normal stage
   but seems like I got taper error. This is the latest. I haven't solve the
   previous error. *** A TAPE ERROR OCCURRED: [No writable valid tape found].
   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: DailySet1-13. [...] 

Content analysis details:   (9.2 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 2.6 WHOIS_MONIKER_PRIV     URL registered to Moniker Privacy Protection
                            [URIs: domain9.com]
 0.2 WHOIS_MYPRIVREG        URL registered to myprivateregistration.com
                            [URIs: nabble.com]
 2.1 URIBL_WS_SURBL         Contains an URL listed in the WS SURBL blocklist
                            [URIs: domain11.com]
 2.0 URIBL_BLACK            Contains an URL listed in the URIBL blacklist
                            [URIs: domain3.com]
 2.4 DNS_FROM_OPENWHOIS     RBL: Envelope sender listed in bl.open-whois.org.


--- Begin Message ---
Subject: Re: amstatus: no estimate and disk was stranded on waitq
From: fedora <zuki AT abamon DOT com>
To: amanda-users AT amanda DOT org
Date: Mon, 23 Jul 2007 23:00:05 -0700 (PDT)
Hello,

Yesterday 23 July 2007 the backup still in normal stage but seems like I got
taper error. This is the latest. I haven't solve the previous error.

*** A TAPE ERROR OCCURRED: [No writable valid tape found].
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: DailySet1-13.

FAILURE AND STRANGE DUMP SUMMARY:
  domain11.com     /var/lib/mysql  lev 0  FAILED [can't switch to
incremental dump]
  domain15.com       /var/lib/mysql  lev 1  STRANGE 
  domain12.com    /var/lib/mysql  lev 2  STRANGE 
  domain13.com       /var/lib/mysql  lev 1  STRANGE 
  domain2.com       /var/lib/mysql  lev 1  STRANGE 
  domain8.com      /var/lib/mysql  lev 1  STRANGE 
  domain10.com  /var/lib/mysql  lev 1  STRANGE 
  domain3.com   /var/lib/mysql  lev 1  STRANGE 
  domain14.com      /var/lib/mysql  lev 1  STRANGE 
  domain1.com    /var/lib/mysql  lev 1  STRANGE 


STATISTICS:
                          Total       Full      Incr.
                        --------   --------   --------
Estimate Time (hrs:min)    0:00
Run Time (hrs:min)        10:52
Dump Time (hrs:min)       43:05       0:00      43:05
Output Size (meg)        5058.8        0.0     5058.8
Original Size (meg)     20728.9        0.0    20728.9
Avg Compressed Size (%)    24.4        --        24.4   (level:#disks ...)
Filesystems Dumped           25          0         25   (1:21 2:4)
Avg Dump Rate (k/s)        33.4        --        33.4

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

Chunks Taped                  0          0          0
Avg Tp Write Rate (k/s)     --         --         -- 


FAILED AND STRANGE DUMP DETAILS:

.... output truncated .....


NOTES:
  planner: tapecycle (14) <= runspercycle (14)
  planner: Preventing bump of domain1.com:/var/lib/mysql as directed.
  planner: Preventing bump of domain2.com:/var/lib/mysql as directed.
  planner: Preventing bump of domain3.com:/var/lib/mysql as directed.
  planner: Preventing bump of domain4.com:/var/lib/mysql as directed.
  planner: Last full dump of domain5.com:/var/lib/mysql on tape DailySet1-04
overwritten in 5 runs.
  planner: Last full dump of domain6:/var/lib/mysql on tape DailySet1-03
overwritten in 4 runs.
  planner: Last full dump of domain7.com:/var/lib/mysql on tape DailySet1-01
overwritten in 2 runs.
  planner: Last full dump of domain8:/var/lib/mysql on tape DailySet1-03
overwritten in 4 runs.
  planner: Last full dump of domain9.com:/var/lib/mysql on tape DailySet1-03
overwritten in 4 runs.
  planner: Preventing bump of domain10:/var/lib/mysql as directed.
  taper: slot 12: read label `DailySet1-12', date `20070723103151'
  taper: cannot overwrite active tape DailySet1-12
  taper: slot 13: not an amanda tape (Read 0 bytes)
  taper: slot 14: read label `DailySet1-14', date `20070714213001'
  taper: cannot overwrite active tape DailySet1-14
  taper: slot 1: read label `DailySet1-01', date `20070715213001'
  taper: cannot overwrite active tape DailySet1-01
  taper: slot 2: read label `DailySet1-02', date `20070716213001'
  taper: cannot overwrite active tape DailySet1-02
  taper: slot 3: read label `DailySet1-03', date `20070716221952'
  taper: cannot overwrite active tape DailySet1-03
  taper: slot 4: read label `DailySet1-04', date `20070717213001'
  taper: cannot overwrite active tape DailySet1-04
  taper: slot 5: read label `DailySet1-05', date `20070718050529'
  taper: cannot overwrite active tape DailySet1-05
  taper: slot 6: read label `DailySet1-06', date `20070718213001'
  taper: cannot overwrite active tape DailySet1-06
  taper: slot 7: read label `DailySet1-07', date `20070719031513'
  taper: cannot overwrite active tape DailySet1-07
  taper: slot 8: read label `DailySet1-08', date `20070719213002'
  taper: cannot overwrite active tape DailySet1-08
  taper: slot 9: read label `DailySet1-09', date `20070720213001'
  taper: cannot overwrite active tape DailySet1-09
  taper: slot 10: read label `DailySet1-10', date `20070721213001'
  taper: cannot overwrite active tape DailySet1-10
  taper: slot 11: read label `DailySet1-11', date `20070722213001'
  taper: cannot overwrite active tape DailySet1-11
  taper: changer problem: 11 file:/backup/amanda/dumps/tape11
  big estimate: domain1.com /var/lib/mysql 2
                est: 569M    out 459M
  big estimate: domain2.com /var/lib/mysql 1
                est: 0M    out 0M
  small estimate: domain5.com /var/lib/mysql 1
                  est: 466M    out 596M


DUMP SUMMARY:
                                       DUMPER STATS               TAPER
STATS 
HOSTNAME     DISK        L ORIG-MB  OUT-MB  COMP%  MMM:SS   KB/s MMM:SS  
KB/s
-------------------------- -------------------------------------
-------------
domain4 -/lib/mysql 1    5782    1307   22.6  651:09   34.3   N/A    N/A 

.................. output truncated ............

domain11 -/lib/mysql 0 FAILED --------------------------------------------

(brought to you by Amanda version 2.5.1p3)

Questions:
1) "No writable valid tape found". What does it mean?
2) Do I need to run amflush? I found out a folder in holding disk dated 23
July 2007.
3) "can't switch to incremental dump". What does it mean? (causing failed
for the dump summary "domin11 -/lib/mysql 0 FAILED......." )
4) "cannot overwrite active tape DailySet1*".  What does it mean?
5) "taper: changer problem: 11 file:/backup/amanda/dumps/tape11". What does
it mean?
6) For  big/small estimate, What is the different between them? As I know
level 0 is full backup, level 1 is incremental and what about level 2?
7) Lastly, all my client servers got N/A result for the taper stats accept
domain11. Why?

Can u guys explain to all the questions? I have been backing up for 1 month
ago but since a few days ago , I encountered these problem. Very appreciate
ur helps.

fedora wrote:
> 
> Dear Marc Muehlfeld,
> 
> After I increased etimeout (300s to 1800s), I found no "planner: [hmm,
> disk was stranded on waitq]" error on amstatus. But now I am having bigger
> problem. All my servers return "no estimate" with level 0. What should I
> do guys??
> 
> 
> fedora wrote:
>> 
>> hi guys,
>> I am having problem with my amanda status. Here are the details:
>> 
>> [amanda@san ~]$ amstatus DailySet1
>> Using /usr/local/etc/amanda/DailySet1/amdump.1 from Thu Jul 19 03:15:13
>> MYT 2007
>> 
>> domain1.com:/var/lib/mysql   1      549m flushed (3:15:38)
>> domain1.com:/var/lib/mysql   1     1301m finished (8:26:06)
>> domain2.com:/var/lib/mysql        0        0m finished (6:43:04)
>> domain3.com:/var/lib/mysql 0       23m finished (6:55:13)
>> domain4.com:/var/lib/mysql   0 planner: [hmm, disk was stranded on waitq]
>> domain5.com:/var/lib/mysql      0           no estimate
>> domain6.com:/var/lib/mysql      0           no estimate
>> 
>> This is the first time I received this error. Amanda has finished backup
>> but I did not receive the report via email. Anyone can help me to explain
>> on this (no estimate and disk was stranded on waitq)?? 
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/amstatus%3A-no-estimate-and-disk-was-stranded-on-waitq-tf4108528.html#a11757384
Sent from the Amanda - Users mailing list archive at Nabble.com.


--- End Message ---