Of course, you are aware that you LM must always be at the highest major level? So 6.1 lib client with 5.5 LM is not supported.
On 22 apr 2010, at 21:00, Zoltan Forray/AC/VCU wrote: > I am starting to see more and more of these errors on my 6.1.3.3 server: > > 4/22/2010 1:58:23 PM ANR9999D_1141620605 pvrOpen(pvr.c:1376) > Thread<51658>: Attempt to open volume with conflicting device class IDs: > 1, 2 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> issued message 9999 from: > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000c0df02 > OutDiagToCons+0x0x142 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000c109e4 > outDiagfExt+0x0x194 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000926628 > pvrOpen+0x0xc88 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000b505a2 > AsOpenVol+0x0xb32 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000b4c814 > AsAcquireInputVol+0x0x9d4 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000b22a75 > AsOpenSeg+0x0xd65 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000b9940d > DoOpenSeg+0x0xdd > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000b99973 > SsAuxSrcThread+0x0x393 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x0000000000c7f0d4 > StartThread+0x0x84 > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x000000336b206367 *UNKNOWN* > 4/22/2010 1:58:23 PM ANR9999D Thread<51658> 0x000000336a6d30ad *UNKNOWN* > 4/22/2010 1:58:23 PM ANR1156W Move data process terminated for volume > 087073 - internal server error detected. > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> issued message 1156 from: > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> 0x0000000000c08e3a > outRptf+0x0xba > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> 0x000000000069c8a5 > AfMoveOffsiteVolumeThread+0x0x465 > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> 0x0000000000c7f0d4 > StartThread+0x0x84 > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> 0x000000336b206367 *UNKNOWN* > 4/22/2010 1:58:23 PM ANR9999D Thread<51626> 0x000000336a6d30ad *UNKNOWN* > 4/22/2010 1:58:23 PM ANR0986I Process 460 for MOVE DATA running in the > BACKGROUND processed 771888 items for a total of 67,921,333,337 bytes with > a completion state of FAILURE at 01:58:24 PM. > 4/22/2010 1:58:23 PM ANR0408I Session 23164 started for server HADES > (Linux/x86_64) (Tcp/Ip) for library sharing. > 4/22/2010 1:58:23 PM ANR0409I Session 23164 ended for server HADES > (Linux/x86_64). > 4/22/2010 1:58:23 PM ANR0514I Session 23060 closed volume 086169. > 4/22/2010 1:58:23 PM ANR0408I Session 23165 started for server HADES > (Linux/x86_64) (Tcp/Ip) for library sharing. > 4/22/2010 1:58:23 PM ANR0409I Session 23165 ended for server HADES > (Linux/x86_64). > 4/22/2010 1:58:23 PM ANR0408I Session 23166 started for server HADES > (Linux/x86_64) (Tcp/Ip) for library sharing. > 4/22/2010 1:58:23 PM ANR0409I Session 23166 ended for server HADES > (Linux/x86_64). > 4/22/2010 1:58:23 PM ANR0409I Session 23088 ended for server HADES > (Linux/x86_64). > > The above failure was for a MOVE DATA to reclaim offsite tapes. When it > upchucked, 2-other similar processes failed, at the same time (didn't > want to post everything here). > > I searched and saw that Wanda had a similar issue/question but didn't see > a resolution. > > I thought it might be related to the tape-mounting issue and upgraded one > of my LM servers (HADES) from 5.5.4.1 to 5.5.4.2. My other LM server > (FIREBALL) is still at 5.5.3.0. Wasn't sure if the problem with tape > mounting was introduced in 5.5.4.0 or 5.5.4.1 so I haven't upgraded it, > yet. > > Not sure if this is related or is the cause but the onsite/primary data > for one of the nodes on this copypool tape, was recently move to to TS1120 > tapes vs originally on TS1130 tapes, thus a different LM/deviceclass. > > Any thoughts? Suggestions? > Zoltan Forray > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [email protected] - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html -- Met vriendelijke groeten/Kind regards, Remco Post
