That's correct. There's an open PR about this. If Luke and others keep poking
me about it, maybe I'll get off my butt and fix it.


On Tue, 19 Mar 2002, Dallas N Antley wrote:

> Under NetBSD 1.5.2/SPARC, it appears that the mt(1) program does not
> return the current 'file number' (or 'block number') as part of the
> 'mt stat' command.  I have tested this with a variety of 4mm and 8mm
> tape drives, but both the values seem to allways return '0'.  Is this
> a problem with my hardware, or a known problem with the mt program or
> st driver?
> 
> I apologise if this isn't a SPARC-specific question.  Unfortunately, I
> only have access to SPARC hardware, so I can't test to see if this is
> platform-independant.  I looked through all the docs I could find on
> www.netbsd.org, but to no avail.
> 
> Tested equipment:	Sun4/600, SS10/50
> 			Sun DDS2
> 			IBM EXB-8505 <EXABYTE, IBM-8505, 6D0A>
> 			    density code 140, 1024-byte blocks, write-enabled
> 
> | # mt rew
> | # mt stat
> | SCSI tape drive, residual=0
> | ds=3<Mounted>
> | er=0
> | blocksize: 0 (0, 0, 0, 0)
> | density: 140 (0, 0, 0, 0)
> | current file number: 0
> | current block number: 0
> | # mt rdspos
> | /dev/nrst0: block location 0
> | # tar -b 112 -cf /dev/nrst0 /usr
> | # mt stat
> | SCSI tape drive, residual=0
> | ds=3<Mounted>
> | er=0
> | blocksize: 0 (0, 0, 0, 0)
> | density: 140 (0, 0, 0, 0)
> | current file number: 0
> | current block number: 0
> | # mt rdspos
> | /dev/nrst0: block location 362
> | # mt rew; mt eom
> | # mt stat
> | SCSI tape drive, residual=0
> | ds=3<Mounted>
> | er=0
> | blocksize: 0 (0, 0, 0, 0)
> | density: 140 (0, 0, 0, 0)
> | current file number: 0
> | current block number: 0
> | # mt rdspos
> | /dev/nrst0: block location 363
> 
> Thank you for your time.
> 
> 				Dallas
>