Thursday, May 15, 2008

Issue With NAS Path

I'm hoping someone else has seen this weird behavior with NAS paths and can shed some light on the issue. What I am currently experiencing is constant errors issuing to the actlog of my library controller instance caused by a failed mount/dismount for an NDMP backup. The TSM instance has been rebooted and the path put offline but I am still getting these errors:

05/15/2008 14:51:18 ANR9999D pvrremot.c(488): ThreadId <32> The PVR remote
descriptor is NULL.(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> issued message 9999 from: (SESSION:
24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x0000000100025bf4 outDiagf
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x00000001004cd380
PvrRemoteOpenDrive (SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x000000010025193c
PvrOpenTapeDrive@AF144_48 (SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x0000000100245a0c
PvrOpenTapeDrive (SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x0000000100245930 PvrOpenDrive
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x00000001002a0150 MgrGetIdleVol
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x00000001002a0e78 PerformDismount
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x00000001002a0850
PerformDismountNow (SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x00000001002a0d24 DismountThread
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x000000010000fe5c StartThread
(SESSION: 24492)
05/15/2008 14:51:18 ANR9999D ThreadId <32> 0x090000000040f448 _pthread_body
(SESSION: 24492)

The problem is that support wants me to reboot my Powderhorn, which is just not feasible. ACSLS is not showing anything in the drive and that the drive is available so I don't see how it's a library/ACSLS issue.

Friday, May 09, 2008

My Lack of Recent Posts

I apologize for the lack of posts lately. I would like to let all TSMExpert visitors know I am currently going through some personal issues that have been very hard on me and have been and will continue to take my attentions elsewhere for the next few months. I thank those contributing in the meantime in advance and hope to get back to blogging as soon as I can.