Hi,

Thanks for the suggestion. We didn't find any failed dismounts
of these volumes. (or any successful ones for that matter).

Regards,

Alexander

(The original message was written by me, but sent by Henk)

> Look for msgno=8469 and see if the dismounts have been failing.  I get this
> kind of behavior occasionally and have found that the dismount fails
> (hardware problem) and TSM transiently reports volumes unavailable.
>
>
>
>
>
>                     Henk ten Have
>                     <hthta AT SARA DOT NL       To:     ADSM-L AT VM.MARIST 
> DOT EDU
>                     >                    cc:
>                     Sent by:             Subject:     TSM server problem
>                     "ADSM: Dist
>                     Stor Manager"
>                     <ADSM-L AT VM DOT MAR
>                     IST.EDU>
>
>
>                     06/20/2002
>                     10:17 AM
>                     Please respond
>                     to "ADSM: Dist
>                     Stor Manager"
>
>
>
>
>
>
> I couldn't find an APAR that describes what we have been seeing
> on our 4.2.1.11 (AIX 4.3.3) server during the last few weeks
> so I was wondering if we have discovered new bug.
>
> First we got this message in the activity log:
>
> 06/09/02   10:39:38  ANR1229W Volume 000591 cannot be backed up - volume is
>                       offline or access mode is "unavailable" or
> "destroyed".
>
> We did a 'q vol f=d'. The access mode of the volume was 'Available'
> so we dismissed it as a freak incident until the message repeated
> itself the next day.
>
> This time we opened the (3494) library and verified that the
> volume was in the correct cell.
>
> We tried a 'restore volume' followed by a 'delete volume'.
> The delete failed:
>
> ANR2405E DELETE VOLUME: Volume 000591 is currently in use by
> clients and/or data management operations.
> ANS8001I Return code 14.
>
> At that time there were no processes or sessions that used
> that particular volume. Also we had four other volumes
> that displayed the same behaviour.
> We halted the server and restarted it again which solved
> the problem. The volumes were no longer 'in use'.
> Today we noticed two other volumes that seem to have
> the same problem so I'm beginning to suspect that I've found
> a bug in the server.
>
> All these volumes have one thing in common: When I seacrh
> the activity log for their mounts and dismounts I can't
> find a dismount message after their last mount (before they
> become 'unavailable'). It is as if the volumes are unmounted
> by the library but TSM isn't being notified of this.
>
> Anyone seen this before?
>
> Cheers,
> Henk.


-----------------------------------------------
Alexander Verkooijen        (alexander AT sara DOT nl)
Alexander Verkooijen        (alexander AT sara DOT nl)
Senior Systems Programmer
SARA High Performance Computing