It is called:
Artificial, non-intelligent, unrelated resource locking
Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180
-----Original Message-----
From: Chetan H. Ravnikar [mailto:Chetan.Ravnikar AT SYNOPSYS DOT COM]
Sent: Wednesday, September 25, 2002 9:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: q act says *No match found*
many thanks for the response! Infact in our case, it seems more to what Paul
has mentioned below, we had the TSM server loosing element inventory
information lately in which case the drives were going offline.
A *mttest* came back with junk numbers, and subsequent tests came back
correctlty. Infact we had to re-seat the QIPs on the spectralogic gator.
After care monitoring and trace file analysis, it is claimed that the TSM
server 4.2.20 on solaris is behaving incorrectly and confused, where as the
library seems to have been sending the same answers everytime to a query
from *mttest*
Now we have engg from both Spectra Logics and Tivoli looking into this new
issues we have seen
We have TSM 4.2.20 running on Solaris-2.8
My concern is how does loosing contact to the drives or the picker, will
cause q act to show nothing!!?
Cheers..
On Wed, 25 Sep 2002, Alex Paschal wrote:
>
> Additionally, I've seen this on a bad tape. If you audit a tape and
> get a lot of damaged files, it lists each one to the actlog and can
> slam the actlog to the point where nothing gets posted to it anymore.
> The same can happen during tape->tape migration, reclamation, move
> data, backup stg, etc, if the process spouts an error for each bad
> file it encounters and keeps going. As near as I can tell, it's the
> volume of messages getting posted to the actlog that causes it. The
> only way I know of to clear it is to bounce the server.
>
> This is just one more issue that has caused me to abandon using the q
> actlog command. I use dsmulog files. I find it's much faster, and
> with vi, grep, awk, etc, I can do searches I couldn't dream of doing
> in the actlog. Of course, if you run out of filesystem space for your
> logs because of tons of error messages, then you're in the same boat
> as if you were using the actlog.
>
> Alex Paschal
> Storage Administrator
> Freightliner, LLC
> (503) 745-6850 phone/vmail
>
>
> -----Original Message-----
> From: Seay, Paul [mailto:seay_pd AT NAPTHEON DOT COM]
> Sent: Saturday, September 21, 2002 12:49 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: q act says *No match found*
>
>
> I have seen this problem before. When I saw it, it was because we had
> tape drives getting a lot of fibre channel SCSI errors and causing all
> kinds of locking apparently. You may want to check to make sure
> something like that is not happening.
>
> Paul D. Seay, Jr.
> Technical Specialist
> Naptheon Inc.
> 757-688-8180
>
>
> -----Original Message-----
> From: Chetan H. Ravnikar [mailto:Chetan.Ravnikar AT SYNOPSYS DOT COM]
> Sent: Saturday, September 21, 2002 3:06 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: q act says *No match found*
>
>
> Ok I bounced the server and things look OK, :)
>
>
> On Sat, 21 Sep 2002, Bob Booth - UIUC wrote:
>
> > Date: Sat, 21 Sep 2002 13:04:05 -0500
> > From: Bob Booth - UIUC <booth AT uiuc DOT edu>
> > Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> > To: ADSM-L AT vm.marist DOT edu
> > Subject: Re: q act says *No match found*
> >
> > Hard to tell whats going on. Is this a fresh install of TSM? What
> > version? What platform is it?
> >
> > Do a 'q stat' and check to see what your activity log retention
> > period is.. It is possible to set the ACTLOGRETENTION to 0, thereby
> > turning it off.
> >
> > hope this helps,
> >
> > bob
> >
> > On Sat, Sep 21, 2002 at 10:23:34AM -0700, Chetan H. Ravnikar wrote:
> > > Any help is appreciated,
> > > I am wondering how can this happen, a fully functional server now
> > > does not give any activity log
> > >
> > > please help
> > >
> > > thanks
> > >
> > >
> > > tsm: server1>q act
> > > ANR2034E QUERY ACTLOG: No match found using this criteria.
> > > ANS8001I Return code 11.
> > >
> > > tsm: server1>
|
