I opened a case last night where the same thing happened, but due to the 
holiday, no one noticed for 4 days. :)
The real-life affect, as far as we can see so far, is drives don't get released 
back to the pool.

I'm using 3.4, latest patch. Whatever cluons are gleaned from my suppot call, I 
will share back to this thread.

JF

On Mon, Nov 27, 2000 at 12:19:44PM -0500, Dennis Dwyer spake unto the 
multitudes:
> 
> I recently saw a case where the backup job indicated the job was completed 
> (data writing ended) but the actual job itself did not end. I discovered that 
> it continued to run 4+ additional hours before I finally caught it. I could 
> not KILL them by conventional means. I guess I could have killed them with 
> the UNIX KILL command but because I did not know how the master server was 
> being effected, I chose to re-boot the server. Can anyone tell me what's 
> happing with this and what I can do to prevent it?
> 
> Regards,
> Dennis Dwyer
> 
> Dennis F. Dwyer
> Enterprise Storage Manager
> Tampa Electric Company
> 
> (813) 225-5181  - Voice
> (813) 275-3599  - FAX
> 
> Visit our corporate website at www.tecoenergy.com
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
"Any man page that includes the words "USE AT YOUR OWN RISK. BEWARE OF DOG. 
SLIPPERY WHEN WET" means trouble" - Michael Lucas
Joshua Fielden, Senior Systems Administrator and Backups Team Lead
eXcite@Home, Inc. jfielden AT excitecorp DOT com 650-556-3316