> >... I think it times out because there is over
> >100,000 files and it can't create the file list. ...
>
> Does the whole file system has 100,000 files, or just
> /raid1/production? Using GNU tar, it would only matter what's under
> /raid1/production.
just the /raid/production has the 100,000+ files.
> >I increased the timeout period in the amanda.conf file which I thought
> >would help, but it didn't. ...
>
> Which timeout variable did you adjust? It should have been "etimeout".
yes, that's the one I adjusted.
> I don't understand. If the CPU usage dropped that much, it implies
> the GNU tar might have been done. Did you do a "ps" to see what was
> going on?
Yeah, the gtar process was the one taking up 70% of the CPU, then after
20 minutes it was only using 0.4%. It never finished, I just killed it
so I could run a manual dump command.
> You might also take a look at /tmp/amanda/sendsize*debug.
I checked and there was nothing exciting in there. It only showed the
gtar start and then me killing it.
> >Before amanda, I used dump to do level zero's every night on the
> >/raid1/production directory which worked well. Can I do that with
> >amanda, I don't mind getting a level 0 backup everyday.
>
> I don't think you can do this. Amanda will see that you are using
> "dump" and convert the mount point to a disk name, then pass that to
> "dump" which will do the whole file system.
>
> You could probably do the infamous GNU tar wrapper hack from:
>
> ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper*
I'll give this a shot, thanks.
later,
ajay
----------------------------------------------------------------
Satyajot (Ajay) Sharma
[EMAIL PROTECTED]
Digital Odyssey System Administrator
WWJMD - What would Jim Morrison do.
----------------------------------------------------------------
