Try the attached patch.
Jean-Louis
McGraw, Robert P. wrote:
When I run amstatus --config daily --date
zorn-[13] amstatus --config daily --date
Using /var/amanda/daily/amdump from Fri May 25 07:51:23 EDT 2007
20070525075123 bers:/ 0
Try the attached patch, it remove the '-w10' flags because the irix od
doesn't accept it.
Jean-Louis
Jean-Francois Malouin wrote:
Not sure if this is relevant (first time I label a tape with
2.5.2-20070508 onward) but I got this from amlabel on a test server
running irix 6.5.57m compiled
A quick update. After generating about 15G of debug logs
(chatty! :-) ), the issue hasn't yet recurred. I'm going to continue
to beat on it to see if I can cause it to occur again. When and if
that happens I'll assemble debug logs covering the crash. Hopefully,
whatever was happening is
Hi,
After enabling 'autoflush' in amanda.conf, and
starting new amdump, I saw two entries for a backup
job that was already on holding disk. One was waiting
to be flushed, the other was getting estimates. (I
had to kill the job
since I didn't want to run the 500GB backup again!).
With
James Brown wrote:
Hi,
After enabling 'autoflush' in amanda.conf, and
starting new amdump, I saw two entries for a backup
job that was already on holding disk. One was waiting
to be flushed, the other was getting estimates. (I
had to kill the job
since I didn't want to run the 500GB backup
E, 28 mai 2007 kirjutas James Brown [EMAIL PROTECTED]:
After enabling 'autoflush' in amanda.conf, and
starting new amdump, I saw two entries for a backup
job that was already on holding disk. One was waiting
to be flushed, the other was getting estimates. (I
had to kill the job
since I
On May 28, 2007, at 11:36 AM, James Brown wrote:
Hi,
After enabling 'autoflush' in amanda.conf, and
starting new amdump, I saw two entries for a backup
job that was already on holding disk. One was waiting
to be flushed, the other was getting estimates. (I
had to kill the job
since I
