>> On Mon, 13 Nov 2006 16:01:57 -0600, Mark Stapleton <[EMAIL PROTECTED]> said:
> [ Crash crash crash ]
> Anyone seen anything like this?
Here are the notes in the status log I keep for my open PMRs. My
business partner is theoretically nudging support too.
62069 442 000: Crash in journal-based-backup. Crashed TSM2!
2006-08-09: opened
2006-08-12: POssible fix. D'oh, crashed usenet!
2006-09-18: Here's a development library. Give it a shot
2006-09-19: D'oh, crashed usenet! Back in development again.
2006-09-17: D'oh, crashed usenet! Back in development again.
3006-10-04: Got the new version in, seems to be OK.
2006-10-07: D'oh, crashed usenet! Grumble.
2006-10-10: Not a filepath problem; punt to AIX.
2006-10-10: No, it's a filepath problem. Back in development.
2006-10-18: No particular update.
2006-10-25: No particular update.
After the first crash, the box I offered up is our USENET server.
While technically a production service, it presents the least
disruption of any box we might choose to crash; so I'm willing to try
experimental stuff on it. The first time, it got my TSM server
hardware, with all 10 TSM server processes on it. I was Not Pleased
at that point, I tell you. ;)
Ran the code uneventfully for a few weeks on a test box before we got
to this point.
- Allen S. Rout
