Richard -
thanks for answering; I checked your ideas, this is the result:
There was a reboot of the tl 2 hours before this happened, but all drives
worked fine (succesful archives) after that reboot.
So I don't think the error depends on that.
As the error occured, I did some q in tsm and I found "path onl=no", and I
made an "update path onl=yes".
Since that everything works fine.
The actlog showed the following messages during that error, for all our 4
drives:
ANR8848W Drive TAPEx of library LIB3583 is inaccessible;
server has begun polling drive.
ANR8300E I/O error on library LIB3583 (OP=C0246C02,
CC=200, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**,
Description=The device indicated a failure
condition, but
sense data was unavailable).
ANR0535W Transaction failed for session 6916 for node
BRZ1SRVBK1 (Linux86) - insufficient mount points
available to satisfy the request.
I also found some error logs from "IBMtape..." on the OS in /var/log. They
are not only from that error day.
And for the moment I don't know, what process is writing these files.
I am not the sysadmin of the machines, so I have to ask the sysadmins about
those logfiles. Sure, there is something to learn.
Best regards, Dierk
|---------+--------------------------->
| | Richard Sims |
| | <rbs AT BU DOT EDU> |
| | Gesendet von: |
| | "ADSM: Dist Stor|
| | Manager" |
| | <[email protected]|
| | T.EDU> |
| | |
| | |
| | 15.03.2006 12:53|
| | Bitte antworten |
| | an "ADSM: Dist |
| | Stor Manager" |
| | |
|---------+--------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| An: ADSM-L AT VM.MARIST DOT EDU
|
| Kopie:
|
| Thema: Re: [ADSM-L] path gone
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Dierk - The answer should be in your server Activity Log, if not also
your OS error log.
The cause is usually hardware problems; in your case, whatever is common
to the pathing, as for example a SCSI cable come loose, the library
being powered off by an operator, etc.
Richard Sims
On Mar 15, 2006, at 2:54 AM, Dierk Harbort wrote:
> Hi all!
>
> We are running TSM 5.2.x on Linux, 1 Server; TL3583 with 4x LTO3
> drives;
>
> My question is:
>
> What could cause, during normal business, the tsm server to set all
> its
> path' to online=no ? (shown in q path)
>
> Has anybody a reason for this?
>
>
> TIA, Dierk
|
