Andrew Raibeck wrote:
> Some thoughts:
>
> - Have you reviewed the entire activity log since the time this volume was
> created (20 October, based on volume history information)? A good starting
> point would be to query the activity log for all messages containing that
> volume name. You'll also want to look for any related messages before and
> after messages containing that volume name.
>   

Unfortunately, we only keep a day's worth of activity logs. Here's what
it shows for the past day:

===

10/25/06   17:34:53      ANR1182I Removable volume 5009L is required for
a restore
                          request from session 1590. (SESSION: 1590)
10/25/06   17:44:23      ANR8337I LTO volume 5009L mounted in drive LTO0
                          (/dev/IBMtape0). (SESSION: 1590)
10/25/06   17:44:23      ANR0510I Session 1590 opened input volume
5009L. (SESSION:
                          1590)
10/25/06   17:44:39      ANR0514I Session 1590 closed volume 5009L.
(SESSION: 1590)
10/25/06   17:53:55      ANR2017I Administrator ADMIN issued command:
QUERY ACTLOG
                          search=5009L  (SESSION: 1593)

===



> - The QUERY VOLUME info you mentioned in a prior post shows a last read
> date of yesterday, about half past noon. Maybe look at the activity log in
> detail around that time frame to see what was going on.
>   

That was me auditing the volume to see if I could get things going again.

> - Have you tried auditing the library?
>   

That seemed to do the trick. I'm not sure why, because the volume was
already listed in "query libvolume"'s output. I checked the output the
output of "q vol 5009L f=d" and "q vol * 5009L f=d" and it was identical
to before. Checking the activity log gave the same messages as before as
well.

-- 
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- K324, (206)-685-7354
-- University of Washington Medical Center