Just to update this. I tried it again (choosing a different directory and in the foreground). This is the current ps -ef |grep amanda:
amanda 30890 30809 76 17:13 pts/0 00:02:23 amflush -f normal amanda 30891 30890 0 17:13 pts/0 00:00:00 driver normal nodump amanda 30892 30891 0 17:13 pts/0 00:00:00 taper normal amanda 30893 30892 0 17:13 pts/0 00:00:00 taper normal In addition this is the current output from the job: Flushing dumps in 20041207 to tape drive "/dev/nst0". Expecting tape Normal20 or a new tape. (The last dumps were to tape Normal19) Are you sure you want to do this [yN]? y amflush: datestamp 20041208 driver: pid 30891 executable driver version 2.4.3 taper: pid 30892 executable taper version 2.4.3 driver: send-cmd time 5.087 to taper: START-TAPER 20041208 driver: adding holding disk 0 dir /var/holding size 296960 reserving 296960 out of 296960 for degraded-mode dumps taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400df000 taper: buffer[01] at 0x400e7000 taper: buffer[02] at 0x400ef000 taper: buffer[03] at 0x400f7000 taper: buffer[04] at 0x400ff000 taper: buffer[05] at 0x40107000 taper: buffer[06] at 0x4010f000 taper: buffer[07] at 0x40117000 taper: buffer[08] at 0x4011f000 taper: buffer[09] at 0x40127000 taper: buffer[10] at 0x4012f000 taper: buffer[11] at 0x40137000 taper: buffer[12] at 0x4013f000 taper: buffer[13] at 0x40147000 taper: buffer[14] at 0x4014f000 taper: buffer[15] at 0x40157000 taper: buffer[16] at 0x4015f000 taper: buffer[17] at 0x40167000 taper: buffer[18] at 0x4016f000 taper: buffer[19] at 0x40177000 taper: buffer structures at 0x4017f000 for 240 bytes taper: read label `Normal20' date `X' I hope this sheds some lite on the matter. I did notice date `X' comment that confuses me somewhat... Paul Bijnens <[EMAIL PROTECTED]> wrote: > James Marcinek wrote: > > > > I've recently deployed amanda. The client forgot tapes on several occasions and > > I've got 4 backups in my holding area. I initiated the amflush command and > > followed the instructions. The job kicked off in the background and I've been > > using: > > > > ps -ef |grep amanda > > > > to see if the process is still running, which it is. When I do a top command > > it's using lots of CPU time. > > Which process is taking CPU time? planner? driver? taper? > > > > > It's been runninng for several hours now and my logs haven't been populating > > since it started. Here's the last few entries: > > > > START amflush date 20041207 > > START driver date 20041207 > > START taper datestamp 20041207 label Normal18 tape 0 > > > > I'm a bit confused because I now see a folder 20041207 in my /var/holding. It's > > empty, which is good if it's working properly. > > For flush, that's normal. > > > > > Why isn't anything being populated too(amflush and log file)? Is there any way > > to tell if it's running properly? > > On linux: strace -p The-PID > on Solaris: truss -p The-PID > > "lsof -o the-PID" tells you which files are opened, and sometimes can > give a hint what it is doing (e.g. which file it is reading/writing). > > (hit Ctrl-C to stop it). > > PS. have also a look at "autoflush on": when forgetting a tape once, > the next time, amanda flushes automatically. > > -- > 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: [EMAIL PROTECTED] > *********************************************************************** > * 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 * > *********************************************************************** > -- James Marcinek Systems Engineer JEMConsult.biz, Inc 813.416.1324