Date: Mon, 10 Feb 1997 11:50:02 -0800 (PST) From: Peter Mutsaers <plm@xs4all.nl> To: freebsd-bugs Subject: Re: kern/2698: scsi tape driver problem Message-ID: <199702101950.LAA20963@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/2698; it has been noted by GNATS.
From: Peter Mutsaers <plm@xs4all.nl>
To: Julian Elischer <julian@whistle.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/2698: scsi tape driver problem
Date: Mon, 10 Feb 1997 18:54:10 +0100 (MET)
>> On Sun, 09 Feb 1997 12:46:23 -0800, Julian Elischer
>> <julian@whistle.com> said:
JE> Peter Mutsaers wrote:
JE> try always using nrst0 for all operations.. I never use rst0
In fact I did. Then I did a mt -f /dev/nrst0 rewind and tried to restore.
For the bugreport I tried with /dev/rst0 instead.
It doesn't make a difference.
My tapedrive is not broken. It works without such problems on Linux
and NT4.0. (Maybe because Linux doesn't treat it as a raw device?)
It is a DEC TZK:
st0 at scbus0 target 2 lun 0
st0: <DEC TZK10 00B3> type 1 removable SCSI 2
st0: Sequential-Access
st0: asynchronous.
density code 0x0, drive empty
This is exactly the same as a Wangtek 525MB drive, I think the Wangtek
5525 ES.
Could/should I tell the driver that it is a Wangtek? The handbook
says:
This drives quirks are known and pre-compiled into the scsi tape device driver
(st(4)).
--
Peter Mutsaers | Abcoude (Utrecht), | Trust is a good quality
plm@xs4all.nl | the Netherlands | for other people to have
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702101950.LAA20963>