Ray / Wanda,
Yes, sometimes a client session can reserve a volume. But I've seen in TSM
5.1 that the process that reserved the drive just takes longer to release
it.
We do multi-process migration and storage pool backups. After the last
individual process finishes, it takes as much as two minutes or more before
TSM reports the entire activity being complete. During that in-between
time, there is nothing running, but the affected drives still show as being
in use. For example, if you try to force a volume dismount, TSM will
report the volume being "not idle."
If your system is doing a lot of paging - ours isn't - the 2+ minute delay
could get significantly longer, during which time it appears that you have
resources reserved while TSM is doing nothing.
That delay seems to have gotten quite a bit longer compared to TSM 4.1. I
have no idea how 4.2 worked in this regard since we did not use that
release.
We haven't reported it to IBM because we know if we just wait it will fix
itself and we seldom get so busy that a couple of minutes is significant.
Tab Trepagnier
TSM Administrator
Laitram, LLC
|---------+---------------------------->
| | "Prather, Wanda" |
| | <[EMAIL PROTECTED]|
| | UAPL.EDU> |
| | Sent by: "ADSM: |
| | Dist Stor |
| | Manager" |
| | <[EMAIL PROTECTED]|
| | .EDU> |
| | |
| | |
| | 09/23/2003 12:44 |
| | PM |
| | Please respond to|
| | "ADSM: Dist Stor |
| | Manager" |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: dismount volume in use?
|
>---------------------------------------------------------------------------------------------------------------|
Next time it happens, try : q session f=d
That will show you if a client restore session still has the tape mounted.
-----Original Message-----
From: -ray [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2003 7:21 PM
To: [EMAIL PROTECTED]
Subject: dismount volume in use?
All,
TSM 5.1.7.2 on AIX 4.3.3, 3570 library. I have a curious problem in that
occasionally, when TSM finishes a process, it fails to mark a 3570 volume
status as IDLE. It remains IN USE, so is never dismounted, and ties up
the drive. So reclamations just sit there (waiting for multiple mount
points), and in a few days when scratch tapes are gone, backups start
failing.
There are no AIX errors, TSM errors, or library hardware errors. The tape
stays in the drive, and TSM says its IN USE, but never uses it.
Anyone seen this before? Is there a way to see what has the volume IN
USE? Change it to IDLE? Or forcibly dismount the IN USE volume? The only
fix i have found is to halt and restart TSM. Not an optimal solution for
us. Thanks for any info.
tsm: TSM>q proc
ANR0944E QUERY PROCESS: No active processes found.
ANS8001I Return code 11.
tsm: TSM>q req
ANR8346I QUERY REQUEST: No requests are outstanding.
ANS8001I Return code 11.
tsm: TSM>q mount
ANR8329I LTO volume ABA426 is mounted R/W in drive TAPE6 (/dev/rmt6),
status: IDLE.
ANR8330I 3570 volume 006BF3 is mounted R/W in drive TAPE2 (/dev/rmt2),
status: IN USE.
ANR8334I 2 matches found.
ray
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean http://www.r-a-y.org
Systems Engineer Southeastern Louisiana University
IBM Certified Specialist AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
