From owner-freebsd-scsi Wed Apr 28 8:55:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay1.mail.uk.psi.net (relay1.mail.uk.psi.net [154.32.105.6]) by hub.freebsd.org (Postfix) with ESMTP id 6BC0015768 for ; Wed, 28 Apr 1999 08:55:21 -0700 (PDT) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay1.mail.uk.psi.net with smtp (Exim 2.02 #3) id 10cWg4-0005TK-00 for freebsd-scsi@FreeBSD.ORG; Wed, 28 Apr 1999 16:55:13 +0100 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) id 80256761.00572DA9 ; Wed, 28 Apr 1999 16:52:13 +0100 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: freebsd-scsi@FreeBSD.ORG Message-ID: <80256761.00572CBF.00@mail.plasmon.co.uk> Date: Wed, 28 Apr 1999 16:52:10 +0100 Subject: Re: QIC tape problems on -stable (was: hanging `tar xfvR /dev /nrst0' process, can i debug it?) Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >These are *amazingly* broken drives then. The SCSI specification says that >a write of *zero* filemarks is to flush any pending writes. You have to do >this when you do a read hardware position in order to avoid an ambiguity >in the spec as to the true position as affected by data in the tape drive >buffer. Doesn't Read Position (34h) give all the info you need, i.e. Physical pos., logical pos. and number of blocks in buffer? I agree that flushing is safer, but surely one could avoid it if necessary. Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message