Thank you very much for your problem report.
It has the internal identification `kern/12062'.
The individual assigned to look at your
report is: freebsd-bugs. 

>Category:       kern
>Responsible:    freebsd-bugs
>Synopsis:       sa tape driver with Cipher 60M SCSI QIC tape drive on 3.2 is droping last 10K block.
>Arrival-Date:   Sun Jun  6 16:20:01 PDT 1999


SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR: 
SEND-PR: Please consult the send-pr man page `send-pr(1)' or the Texinfo
SEND-PR: manual if you are not sure how to fill out a problem report.
SEND-PR:
SEND-PR: Note that the Synopsis field is mandatory.  The Subject (for
SEND-PR: the mail) will be made the same as Synopsis unless explicitly
SEND-PR: changed.
SEND-PR:
SEND-PR: Choose from the following categories:
SEND-PR:
SEND-PR: kern
SEND-PR:
To: FreeBSD-gnats-submit@_ERASE_freebsd.org
Subject: sa tape driver with Cipher 60M SCSI QIC tape drive on 3.2 is droping last 10K block.
From: jhs
cc: nclayton@_ERASE_lehman.com, stuart, gary
Reply-To: jhs@
X-send-pr-version: 3.2


>Submitter-Id:   current-users
>Originator:     Julian H. Stacey jhs@
>Confidential:   no
>Synopsis:       sa tape driver with Cipher 60M SCSI QIC tape drive on 3.2 is droping last 10K block.
>Severity:       serious
>Priority:       medium 
>Category:       kern 
>Release:        FreeBSD 3.2-RELEASE i386
>Class:          sw-bug
>Environment:

        -

>Description:

        I had intended to file a bland 
		Category:	docs
		"please add to docu that this drive still works on 3.2"
	But Not So 
		It seems the driver software has been srambled, & last blocks are dropped on write !

	Cipher tape drive Model 540 (Capacity: QIC 45M 60M tapes, Interface: SCSI 1)

	dmesg reports it as:
		Jun  6 18:48:17 wall /kernel: sa0 at aha0 bus 0 target 3 lun 0
		Jun  6 18:48:17 wall /kernel: sa0: <  > Removable Sequential Access SCSI-CCS device
		Jun  6 18:48:17 wall /kernel: sa0: 3.300MB/s transfers 

	It started to read a tape OK, that I created 1996.01.16 on BSD
		(but I got impatient & didnt read whole tape, as I control C'd it,
		as I thought I was just verifying then)

	On writing a 7.7M directory with 	tar cvf /dev/rsa0 .	at end it reported
		tar: only wrote 0 of 10240 bytes to /dev/rsa0
	On reading same tape
		tar: Unexpected EOF on archive file
	On comparing directories, last file was different,
	to compare directories I used
		find . -type f -exec cmpd -d -v {} ../../public_html \;
	( cmpd.c is written by me (compare & delete), available on 
		http://.............../~jhs/src/bsd/jhs/bin/public/cmpd/ )

	Historical note: This is one of the same drive type I had listed as working in 
		From: burgess@_ERASE_hrd769.brooks.af.mil (Dave Burgess)
		Date: 13 Jan 1994 06:00:46 -0000
		Newsgroups: comp.os.386bsd.announce,comp.answers,news.answers
		Subject: [comp.os.386bsd] BNR/2 derived BSD for PCs FAQ (Part 9 of 10)
		Message-ID: <386bsd-faq-9-758440818@_ERASE_hrd769.brooks.af.mil>

		Archive-name: 386bsd-faq/part9

>How-To-Repeat:

	I do not know if this problem materialises on other drives & densities, I have others 
	(Tandberg & Prime 60M ) & will try them, didn't notice this on my Tandberg 525M drive.

>Fix:
	Driver software needs fixing, meantime:
	Always append 10K of garbage file as last item in a tar write 
	(this is the same horrible trick I used many years ago, that became 
	un-necessary years ago, & now is back again - Uugh ! :-)