From owner-freebsd-stable Wed Aug 28 6:16:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B7C937B401; Wed, 28 Aug 2002 06:16:34 -0700 (PDT) Received: from kazi.fit.vutbr.cz (kazi.fit.vutbr.cz [147.229.8.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07F4443E77; Wed, 28 Aug 2002 06:16:33 -0700 (PDT) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (8.12.5/8.12.5) with ESMTP id g7SDGUls057741 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 28 Aug 2002 15:16:30 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.12.5/8.12.5/Submit) id g7SDGU4h057740; Wed, 28 Aug 2002 15:16:30 +0200 (CEST) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Wed, 28 Aug 2002 15:16:30 +0200 From: Cejka Rudolf To: freebsd-stable@freebsd.org, mjacob@freebsd.org Subject: EOT tape handling changed? Message-ID: <20020828131630.GA56946@fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, since the beginning of August my backup service stopped to work in FreeBSD-stable. Finally I understand why. With the revision scsi_sa.c:1.45.2.12 from Aug 2, the End of Tape is reported by result zero instead of previous -1/ENOSPC after write() call. Now I have two "questions": 1) Why it had to be changed at all? If I look into afbackup sources, it seems that there is no other such OS, which returns written size 0 - it seems to me that atleast Solaris, AIX, Irix, Linux, OSF, HPUX, OpenBSD and NetBSD all return an error -1 and they set errno to ENOSPC (like when there is a full filesystem) or ENXIO. Can anybody confirm it, if it is right? 2) Why it had been changed in -stable too? Why not only in -current? It breaks atleast one backup program (afbackup), which has to be fixed/patched now... -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message