Interesting. (I'll leave aside the issue of how TSM should deal with this
error and whether it should try another tape to continue your backup.) We
also started seeing this same error message a few weeks ago - I'm calling
it the 'double end-of-volume' problem because the root issue seems to be
the 'already reached EOV once' message.
We're at TSM 5.2.3.0 on AIX, so the offsets and line numbers differ from
your symptoms, but it's precisely the same error. In our case, the error
occurred about 10 times over the course of 2 weeks, *always* on the same
tape drive. Since TSM marks the tapes in error status, this was becoming a
problem, so I've set that drive offline to TSM. Poof, no new errors.
We've got a 3584 library with LTO-2 drives; in November, I updated the
firmware for both to then-current levels of 47Q0 for the drives and 4390
for the library (although I see 4680 came out for the library on 2/22/05).
In working on this 'double end-of-volume' problem, I decided it would be
worth udating to the latest version of Atape as well, so I did - we're now
at 9.1.6.0. I see that there's a 9.2.6.0 out there now (although the
associated change history file doesn't even mention it??). I'll probably
upgrade again to these latest levels, but I was wondering...
Has anyone else seen these double EOV messages? I've got an open problem
with IBM hardware support, but none of the double EOV errors showed up in
any of the hardware diagnostics, and there are no Atape dumps associated
with these errors. I find it awfully suspicious that these errors all
occur on the same drive.
Our tape system is getting to be troublesome - these problems started in
the midst of another (unrelated??) series of problems discussed here a few
weeks ago under the subject 'LTO2 corrupted index question'.
Anyone else getting such grief from their 358x tape system??
Thanks,
Bill
Bill Kelly
Auburn University OIT
On Thu, 10 Mar 2005, John E. Vincent wrote:
> Recently we've started seeing these messages pop up when we try to run
> our nightly db2 backup:
>
> 03/10/2005 02:24:25 ANR8337I LTO volume 000002L2 mounted in drive DRIVE0
> AM (/dev/IBMtape0).
>
> 03/10/2005 02:33:49 ANR8341I End-of-volume reached for LTO volume
> 000002L2.
> AM
>
> 03/10/2005 02:33:51 ANR9999D pvrntp.c(2541): ThreadId<18> NtpOpFlush
> error on
> AM drive DRIVE0 (/dev/IBMtape0); already reached
> EOV once.
> Callchain of previous message: 0x08793053
> outDiagf+0x203
> <- 0x08857b37 NtpFlush+0x1d7 <- 0x0885793e
> NtpWrite+0x
> 50e <- 0x08867533 LtoWrite+0x83 <- 0x084c7c5f
>
> AgentThread+0x93f <- 0x0809c53f
> StartThread+0x8f <-
> 0xb759bdac *UNKNOWN* <- 0xb7537a8a *UNKNOWN*
> <-
> 03/10/2005 02:33:51 ANR1411W Access mode for volume 000002L2 now set
> to
> AM "read-only" due to write error.
>
> We're running TSM Version 5, Release 2, Level 2.0 on RHEL 3.0 and DB2 is
> running DB2 8.1FP4.
>
> Thanks for any help!
> John E. Vincent
>
|
