Maurice Poisson Adriasola wrote:

On Jul 1, 2005, at 7:53 AM, Paul Bijnens wrote:
Are you hitting this bug?

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132057


I have been hitting it in hosts with very little physical memory. Maybe there is barely enough memory on this host too. I'm gonna check it.

Could be another clue.  The hosts where it does work here, have plenty
of RAM (1 Gbyte).
The host where I disabled it has 256 Mbyte.

I never noticed the regularity -- once every two runs -- or is that just
a rough proportion of the crashes/successes?


It has been once every two runs (or once every 48 hours) if and only if the amdump-wrapper script is launched by cron (as user backup). Instead, if the same script is run as a shell job by user backup, it can be run more times without failure.

I seem to remember this also:  I could hardly get the bug when
I executed my scrips manually -- tens of times after another.
But when running at night with cron, I almost could bet it crashed the computer. (Luckily I lost my hair before already.)


Failure seems to happen only every time amanda's planner schedules an incremental backup of the (snapshoted) /var filesystem and never when a full dump is due.


Do you use gnutar or dump for backup?


--
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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************


Reply via email to