Amanda-Users

Re: Problem with amflush

2004-02-05 07:22:59
Subject: Re: Problem with amflush
From: Paul Bijnens <paul.bijnens AT xplanation DOT com>
To: Rohit <rohit AT genetechindia DOT com>
Date: Thu, 05 Feb 2004 13:14:39 +0100
Rohit wrote:

Ok. Can I create one more directory under /backup, set permissions, move
all dumps from /backup into the new directory and run amflush again? Will
that be okay?

No, unless you don't have any chunked files.

The header of contination chunk file in holdingdisk contains an
abolute pathname (that way amanda could place chunks of one backup
over different holdingdisks).

Here are the contents of amflush:

amflush: datestamp 20040205
driver: pid 7545 executable driver version 2.4.3
driver: send-cmd time 0.098 to taper: START-TAPER 20040205
taper: pid 7546 executable taper version 2.4.3
taper: page size is 4096
taper: buffer size is 32768
taper: buffer[00] at 0x400d5000
...
taper: buffer[19] at 0x4016d000
taper: buffer structures at 0x40175000 for 240 bytes

Somewhere around these lines, I would expect the instructions like
FLUSH host /d/l/e 20040204 /holding/disk/20040204/host._d_l_e.0
These are missing...  And of course, nothing happens.

taper: read label `Set-1-08' date `20040108'
taper: wrote label `Set-1-08' date `20040205'
driver: adding holding disk 0 dir /backup size 572408
reserving 572408 out of 572408 for degraded-mode dumps

Then it sits idle, still waiting for the above instructions...
And almost 2 hours gives up:

driver: start time 6317.511 inparallel 4 bandwidth 2000 diskspace 572408 dir
...


You'll have to find out why there is no schedule generated.
The schedule is generated by "amflush" and piped into "driver".
Is there a core dump in /tmp/amanda or in ~/amanda/TheConfig ?
Can you find out if they are running?  And what it's doing?

Try:  strace -p pid-of-the-process

(for amflush and driver)
Which one is taking CPU?  I guess amflush.

Try to examine a core file to find out what it was doing:
  $ ulimit -c unlimited
  $ amflush ....

and in another window, as amanda or root:

  $ kill -3 pid-of-amflush

and then, cd to where the core file is found (current directory,
or /tmp/amanda or ~amanda/TheConfig, I'm not sure), and
get a stacktrace:

  $ gdb /usr/sbin/amflush core
  gdb>  bt
  ....

And send me this output.
--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************


<Prev in Thread] Current Thread [Next in Thread>