John,

Thank you very much for the response.  I am sorry for the lack of
details....but on the info below where you mentioned that I didn't give the
level 1...that was actually all that consisted of the log.  Does that tell
you anything?

Does the disk having a problem seem like the most logical from your
perspective?  This is about a $6-8,000 telenet 6 disk raid 5 array with 10k
scsi drives and a 80mbit adaptec scsi2 card.  The system is overall slow as
a dog.  This is odd to me because it is a thunderbird 900 with 512mb memory.
I cannot figure this whole thing out.

What do you all think.

Thank you very much,
Jeff

-----Original Message-----
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 06, 2001 5:19 PM
To: Jeff Heckart
Cc: [EMAIL PROTECTED]
Subject: Re: large filesystem problems


>4- How would I find the version of dump that I am using?  ...

I wouldn't know.  I just remember (from stories posted here) that on
Linux, you want the latest and greatest because old versions had a lot
of trouble.

>sendsize: debug 1 pid 5846 ruid 213 euid 213 start time Fri Apr  6 07:07:11
>2001
>/usr/local/libexec/sendsize: version 2.4.2p1
>calculating for amname 'sd0a', dirname '/'
>sendsize: getting size via dump for sd0a level 0
>sendsize: running "/sbin/dump 0sf 1048576 - /dev/rsd0a"
>running /usr/local/libexec/killpgrp
>  DUMP: Date of this level 0 dump: Fri Apr  6 07:07:11 2001
>...
>sendsize: running "/sbin/dump 0sf 1048576 - /dev/rsd0h"
>running /usr/local/libexec/killpgrp
>  DUMP: Date of this level 0 dump: Fri Apr  6 07:07:17 2001

Note that it only took 6 seconds to get the level 0 estimate of "/".

>sendsize: running "/sbin/dump 1sf 1048576 - /dev/rsd0h"
>running /usr/local/libexec/killpgrp
>  DUMP: Date of this level 1 dump: Fri Apr  6 08:15:26 2001

But it took 1:08:09 to get the level 0 estimate of "/usr".  And since
you didn't post anything else, I assume the level 1 estimate took a long
while as well.

It's strange a level 0 estimate would take that long.  They are usually
reasonably quick since they don't have to do much groping around.  I think
I'd start checking into the health of that disk, or the controller,
cables, etc.

>The other odditty is i have dtimeout set for 10000 in amanda.conf.  Why
>would the estimate be only 45min??

The dtimeout variable has to do with when the dump is actually being run,
not the estimate.  For that, you want the etimeout variable.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Reply via email to