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#a11704398
Sent from the Amanda - Users mailing list archive at Nabble.com.