[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference stkhlm::magtape

Title:	MAGNETIC TAPEDRIVES

Moderator:	STKHLM::GJOHNSSON

Created:	Mon Sep 21 1987
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3775
Total number of notes:	13147

3676.0. "Exabyte 8200 OpenVMS Alpha 6.2-1h3, problem reading subsequent savesets" by KAOT01::B_BUTLER () Thu Feb 27 1997 02:01

	Has anyone seen a problem with an exabyte 8200 having problems reading
any savesets other than the 1st ? My customer is running OpenVMS Alpha 6.2-1h3
on an Alpha 2100. He has the latest exabyte firmware and has the alpscsi02-070
patch installed. There is no problem writing subsequent savesets but they 
cannot be read afterwards even with a backup/list. When they attempt to read one
the drive locks up and the device is no longer accessible. This drive was also 
moved to a Vax running 5.5-2 and functions perfectly. If anyone has seen this or
has any ideas please respond.

Thanks,
Brian Butler

T.R Title User Personal
Name Date Lines

3676.1 Try later patch STAR::S_SOMMER Fri Feb 28 1997 17:42 7

T.R	Title	User	Personal Name	Date	Lines
3676.1	Try later patch	STAR::S_SOMMER		`Fri Feb 28 1997 17:42`	7
	Just last week a fix was checked into OpenVMS to handle a blocking size problem with the Exabyte 8200 drives. This is a problem that could occur on Alpha V6.2 or later, as well as on VAX V7.1. Basically the drive was operating in fixed block size mode when it should have been doing variable blocking. So this patch seems worth a try. Sue

    Just last week a fix was checked into OpenVMS to handle a blocking size
    problem with the Exabyte 8200 drives.  This is a problem that could
    occur on Alpha V6.2 or later, as well as on VAX V7.1.  Basically the
    drive was operating in fixed block size mode when it should have been
    doing variable blocking.  So this patch seems worth a try.
    
    Sue