I've seen this for a couple of versions. I'm a bad boy in that I have not reported it. I think there is some slight bug when a move data starts: a counter is not being zeroed as it should be before the processing starts. As long as the number of unreadable files stays zero I believe you're OK.
Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Cascanette Sent: Wednesday, January 02, 2002 12:24 PM To: [EMAIL PROTECTED] Subject: Re: unreadable bytes I tried it, however it does not show what files had problems moving to another tape. -----Original Message----- From: Malbrough, Demetrius [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 2:07 PM To: [EMAIL PROTECTED] Subject: Re: unreadable bytes Have you tried tsm> q content volname f=d ? -----Original Message----- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 1:07 PM To: [EMAIL PROTECTED] Subject: unreadable bytes Happy new year all... I was freeing up some tapes today and noticed the unreadable bytes number was not zero. Is there any way to determine what files had a problem. The move data's are completing successfully according to the act log. Thanks Joe Cascanette The Cumis Group Limited Server - 4.2.0.6 windows2000 6 Move Data Volume DIX098 (storage pool OFFSITE_DRP), Target Pool OFFSITE_DRP, Moved Files: 1533, Moved Bytes: 5,445,197,341, Unreadable Files: 0, Unreadable Bytes: 152427809. Current Physical File (bytes): 771,036 Current input volume: DIX098. Current output volume: DIX022.
