Date: Tue, 11 Feb 1997 09:45:50 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: plm@xs4all.nl (Peter Mutsaers) Cc: gurney_j@resnet.uoregon.edu (John-Mark Gurney), freebsd-bugs@freefall.freebsd.org Subject: Re: kern/2698: scsi tape driver problem Message-ID: <Mutt.19970211094550.j@uriah.heep.sax.de> In-Reply-To: <199702110000.BAA00374@plm.xs4all.nl>; from Peter Mutsaers on Feb 11, 1997 01:00:53 %2B0100 References: <199702101950.LAA20963@freefall.freebsd.org> <Pine.BSF.3.95q.970210124628.24299G-100000@hydrogen.nike.efn.org> <199702110000.BAA00374@plm.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter Mutsaers wrote: > I did this. The result is that mt -f /dev/rst0 status now reports the > correct densities: > > /sys/scsi# mt -f /dev/rst0 status > Present Mode: Density = QIC-150 Blocksize = 512 bytes > ---------available modes--------- > Mode 0: Density = 0x00 Blocksize variable > Mode 1: Density = QIC-320 Blocksize variable > Mode 2: Density = QIC-150 Blocksize variable > Mode 3: Density = QIC-120 Blocksize variable > > instead of those X3.--- density codes (whatevery they are). That's expected. Note that the Mode 0 through Mode 3 values are simple ``preset profiles'', nothing else. It reports your present mode to be fixed-length 512-byte. But apparently, while the driver attempts to tell this to the drive, your drive doesn't honor this. > Indeed, as Joerg Wunsch said, the QIC 150 tape seems to write variable blocks > instead of 512 byte blocks. (525MB tapes are always variable blocks. I > have no problems at all with them). 525 MB yes. But if your drive doesn't honor the blocksize setting in the buffer header of a MODE SELECT command, it's simply broken. I suggest getting a newer firmware revision. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970211094550.j>