Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Feb 1997 13:24:33 +0100 (MET)
From:      Peter Mutsaers <plm@xs4all.nl>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/2698: scsi tape driver problem
Message-ID:  <199702091224.NAA02128@plm.xs4all.nl>
Resent-Message-ID: <199702091250.EAA15281@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         2698
>Category:       kern
>Synopsis:       After rewind I cannot read a tape; blocksize problems
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb  9 04:50:01 PST 1997
>Last-Modified:
>Originator:     Peter Mutsaers
>Organization:
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

NCR815 SCSI interface, QIC-150 tape (in 525 MB drive)

>Description:

When I've written a dump, and try restore on that dump, I get a read error.

>How-To-Repeat:

$ mt -f /dev/nrst0 status
Present Mode:   Density = QIC-150      Blocksize = 512 bytes
---------available modes---------
Mode 0:         Density = 0x00         Blocksize variable
Mode 1:         Density = X3.136-1986  Blocksize = 512 bytes
Mode 2:         Density = X3.39-1986   Blocksize variable
Mode 3:         Density = X3.54-1986   Blocksize variable
$ dump 1af /dev/rst0 /dev/rsd1f
....
...
$ restore tf /dev/rst0 
tape read error: Input/output error
console output: st0: block wrong size, 64 blocks residual

When I open tapedrive and close it again, I can read with restore t.
But only once. When I try again I get the same error.

Also, I can never read a dump with dd (dd if=/dev/rst0 bs=512 fails):
$ dd bs=512 if=/dev/rst0 of=/dev/null
dd: /dev/rst0: Input/output error
0+0 records in
0+0 records out
0 bytes transferred in 12.830684 secs (0 bytes/sec)

console output: st0: 10240-byte record too big

Although I did specify bs=512!

Note: using tar instead of dump does not cause such problems. So dump
must do something special to the device that triggers the problem.

>Fix:
	
	

>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702091224.NAA02128>