On Wed, Nov 23, 2005 at 05:10:12PM +0100, Jehan PROCACCIA wrote:
> Jon LaBadie wrote:
>
> >On Wed, Nov 23, 2005 at 02:48:14PM +0100, Jehan PROCACCIA wrote:
> >
> >
> >>hello
> >>I use amnda to backup several servers, unfortunatly since a few weeks
> >>ago, indexes for amrecover don't work anymore.
> >>I check the faq-o-matic
> >>http://amanda.sourceforge.net/fom-serve/cache/24.html and I am not in
> >>any cases mentioned
> >>"index yes" is set, amrecover is call with "-C" , and I use Gnu tar
You say you use tar. But your ps output below says otherwise.
> >>tar-1.14-4 on my fedora core 3 backup systeme ( kernel 2.6.10-1.770_FC3
> >>amanda-server-2.4.4p3-4)
> >>Index file are present but empty !
> >>[root@backup /var/lib/amanda/int/index/cobra3/_p2v5f1]
> >>...
> >>-rw------- 1 dumpy disk 20 nov 21 23:02 20051121_3.gz
> >>-rw------- 1 dumpy disk 20 nov 22 23:40 20051122_3.gz
> >>
> >Those are "indexes" of a level 3 dump. I presume there are corresponding
> >level 2, level 1, and level 0 indexes also. Correct?
> >
> yes there are 0 1 2 and 3 levels ... all have a 20 (byte) size !
> >
> >>what is the problem ? advices ?
> >
> >Since the problem is not amrecover, stop focusing on it.
> >Go back to your reports, logs, debug files on server and
> >client to see any problems that occurred.
> >
> >
> While dumping I see these processes on the machine I dump , and the one
> with "sh defunct" alerts me ...?
> [root@cobra3 /mci/mci/test]
> $ ps auwx | grep aman
> amanda 29165 0.0 0.0 2104 804 ? S 15:07 0:00
> /usr/lib/amanda/sendbackup
> amanda 29167 49.6 0.0 1740 632 ? S 15:07 2:23
> /usr/bin/gzip --fast
> amanda 29168 1.5 0.0 2104 780 ? S 15:07 0:04
> /usr/lib/amanda/sendbackup
> amanda 29169 0.0 0.0 0 0 ? Z 15:07 0:00 [sh
> <defunct>]
> amanda 29170 1.6 0.1 6488 4692 ? S 15:07 0:04 dump 0usf
> 1048576 - /dev/emcpowerp1
> amanda 29222 1.5 0.1 6500 4812 ? S 15:08 0:03 dump 0usf
> 1048576 - /dev/emcpowerp1
> amanda 29223 1.7 0.1 6488 4696 ? D 15:08 0:04 dump 0usf
> 1048576 - /dev/emcpowerp1
> amanda 29224 1.7 0.1 6488 4696 ? D 15:08 0:04 dump 0usf
> 1048576 - /dev/emcpowerp1
> amanda 29225 2.0 0.1 6488 4696 ? D 15:08 0:05 dump 0usf
> 1048576 - /dev/emcpowerp1
These lines look like you are running dump, not tar.
The zombie (aka defunct) process may or may not be significant.
I'd guess the latter.
When a process is forked off by its parent, finishes and exits
(normally or ungracefully :), that child becomes a zombie UNTIL
the parent asks to check its exit status. The parent may not
care about the child's exit status or may be busy doing something
else. If the parent never checks the child, which may have run
totally normally, will remain in the process table as a zombie
until the parent exits.
I'm more curious about why there are 5 dump processes working on
the same file system. Is that also what you see on a similar
client that dumps and indexes correctly?
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
