> Tivoli support said to turn on CRCchecking.
> I say, uh yeah, I already know my data is bad.
> Looks like I gotta try and figure out which drive/disk/scsi
> card is causing the problem myself.
Is there any activity log data from the time the data was written to the
problem volume(s) that shows any problems with the writes? If so, then
that would be useful for Level 2 to have. If not, then determining how it
got that way is difficult at best.
I do not believe the suggestion to turn on CRC checking is intended as the
cure. Rather, it is intended as a diagnostic aid to try to catch any new
instances of incorrectly written data as they occur, which would help
pinpoint the problem. (Just my take from my admittedly cursory review of
your PMR.)
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Matthew Glanville <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/23/2003 15:47
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Yikes LTO2 problem!?!
Problem:
Lots and lots of tapes reporting errors when, auditing, copying,
moving
data from them...
06/23/03 10:52:37 ANR9999D pvrntp.c(4586): ThreadId<15> Invalid
block header read from NTP drive DRIVE5 (/dev/rmt/10st).(magic=5A4D4E50,
ver=5, Hdr blk=1450 <expected 1451>, dbytes=262096 <262096>)
(Thus thousands of files on several tapes are unreadable)
TSM Server 5.1.6.3 on Solaris 9 (Sun V880 server)
IBMtape 4.0.7.3
8 LTO2 drives in IBM 3584 library (SCSI not Fiber attached) ( firmware
version 3641)
Hmm, all my testing of filling/restoring a few tapes of data said I could
backup/restore fine...
But the day after the system goes into production and we start moving real
data to these tapes, whammo..
Tivoli support said to turn on CRCchecking.
I say, uh yeah, I already know my data is bad.
Looks like I gotta try and figure out which drive/disk/scsi card is
causing
the problem myself.
Any suggestions?
Thanks
Matt G
