>Number:         370
>Category:       kern
>Synopsis:       Writing to a write-protected SCSI tape doesn't report an error
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   mhw
>Arrival-Date:   Sun Jul 31 00:35:02 1994
>Originator:     Mark Weaver
>Organization:
--------------------------------------------------------------------
Email: Mark_Weaver@brown.edu           | Brown University
PGP Key: finger mhw@cs.brown.edu       | Dept of Computer Science
>Release:        NetBSD 1.0-BETA (27-July-1994)
>Environment:
Gateway 2000 486/DX2-66 VLB, 16mb RAM
Ultrastor 34F VLB

uha0 at isa0 port 0x340-0x9a5 irq 0
scsibus0 at uha0
uha0 targ 0 lun 0: <IMPRIMIS94601-15        4614> SCSI1 direct fixed
sd0 at scsibus0: 992MB, 1931 cyl, 15 head, 70 sec, 512 bytes/sec
uha0 targ 1 lun 0: <ARCHIVE VIPER 2525 25462-007> SCSI1 sequential removable
st0 at scsibus0: rogue, density code 0x0, 1024-byte blocks, write-protected

System: NetBSD cis-ts3-slip4.cis.brown.edu 1.0_BETA NetBSD 1.0_BETA (EXCELSIOR) #1: Sat Jul 30 13:36:57 EDT 1994 mhw@cis-ts3-slip4.cis.brown.edu:/usr/src/sys/arch/i386/compile/EXCELSIOR i386


>Description:
	Writing to /dev/rst0 when a write-protected tape is in the drive
	doesn't report an error.  To be more precise, tar doesn't report
	an error, but I have faith that tar has robust error checking.
	The tar charges ahead (as is visible if the -v flag is given),
	even though the drive neither moves nor writes.  However, the
	drive light is on while the device is open, and turns off as
	soon as the tar is complete.

>How-To-Repeat:
	With a write protected tape in the drive:

	tar cvf /dev/rst0 /usr

>Fix:
>Audit-Trail:
>Unformatted:


------------------------------------------------------------------------------