On Wed, Nov 22, 2017 at 09:35:48 -0500, Jean-Louis Martineau wrote:
> We want to flush the .tmp files.
>
> They are partial dump and they may contains important files, so we want
> to flush them.
> amrecover never restore from partial dump, but they can be manually
> restored.
Ah, got it.
In that case, the details from my original email on this thread (dated
Nov 17) become more important, since it seemed like the taper process
crashed while trying to tape the .tmp file.
When I first saw the errors in the log file I started investigating and
had a theory that the taper program couldn't handle a situation where
the next-chunk referenced in the header of the current file didn't
actually exist, but I did not investigate far enough to confirm that
theory.
Unfortunately the logs from that amflush run have rotated off my system
now, and of course it will be more difficult for me to get amflush to
try flushing .tmp files again now that the pid locking is working, but
let me know if you want me to try to investigate that taper crash further.
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
