Paul Bijnens wrote:
Moliere Christian wrote:
Here it is what amstatus went out on the screen :
Using /usr/local/amanda/dir/local/amdump from Thu Jun 12 09:43:09
CEST 2003
fext01ft:/etc 0 645k finished (9:43:18)
fext01ft:/home/ftp/unix_accounts 0 2695205k dumping 227232k (
8.43%) (9:43:30)
...
Since it is blocked like that at the same value of 8.43% as usual ????
Then you have to find out what your tar_or_dump program on the client
"fext01ft" is doing. Is it advancing? Is it consuming cpu? Is it reading
files or is it blocked and waiting for something that does not happen.
(Like a hard nfs mount of a dead host.)
Here it is log of strace with gtar process :
write(1, "./bac2002/www/corr/arbo/gabarits"..., 57) = 57
write(1, "./bac2002/www/corr/arbo/gabarits"..., 60) = 60
write(1, "./bac2002/www/corr/arbo/gabarits"..., 58) = 58
read(0, "tmargin=\"0\" topmargin=\"0\" margin"..., 10240) = 8192
read(0, "r: #000099;}\nA.BACK {text-decora"..., 2048) = 2048
write(1, "./bac2002/www/corr/arbo/gabarits"..., 64
it is blocked like that
Here it is log of strace on gtar
and lsof on this gtar :
OMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
gtar 1447 root cwd DIR 104,11 4096 983041 /home/ftp/unix_accounts
gtar 1447 root rtd DIR 104,10 1024 2 /
gtar 1447 root txt REG 104,10 150796 38813 /bin/tar
gtar 1447 root mem REG 104,10 485171 61202 /lib/ld-2.2.4.so
gtar 1447 root mem REG 104,10 5772268 22443 /lib/i686/libc-2.2.4.so
gtar 1447 root mem REG 104,10 261460 61236
/lib/libnss_files-2.2.4.so
gtar 1447 root 0r FIFO 0,0 438390950 pipe
gtar 1447 root 1w FIFO 0,0 438390945 pipe
gtar 1447 root 2w FIFO 0,0 438390941 pipe
gtar 1447 root 3r REG 104,9 487 27801
/tmp/amanda/sendbackup.home__ftp__unix__accounts.20030613145308.include
gtar 1447 root 4u REG 104,5 0 16812
/usr/local/amanda/gnutar-lists/fext01fthome_ftp_unix_accounts_0.new
gtar 1447 root 5r DIR 104,9 77824 26369 /tmp/amanda
gtar 1447 root 6r REG 104,11 3780 1523714
/home/ftp/unix_accounts/bac2002/www/corr/bac/arbo/corriges/125812734_24_128_cor_sujet.htm
gtar 1447 root 10w REG 104,9 493 27802
/tmp/amanda/runtar.20030613145308.debug
I did that twice, it blocks in the same directory but not the same file.
I did manualy a tar file as that without any problem :
tar --create --file - --directory ./ --one-file-system --sparse --totals .
and in a file
tar --create --file toto --directory ./ --one-file-system --sparse --totals .
I received the same size of data in my holding disk. Client is a redhat 7.2.
For Solaris, try: "truss -p pid_of_dump_or_tar"
For Linux, try: "strace -p pid_of_dump_or_tar"
(As amanda or root).
Which file or directory is it currently reading?
lsof -p the_pid
or "cd /proc/the_pid" etc.
--
Sincerely,
Cordialement,
Christian MOLIERE
Tél : +33 1 43 60 11 50
Mobile : +33 6 73 37 36 33
|
