From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 27 12:24:44 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BBF016A4BF for ; Wed, 27 Aug 2003 12:24:44 -0700 (PDT) Received: from matou.sibbald.com (matou.sibbald.com [195.202.201.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA04043FD7 for ; Wed, 27 Aug 2003 12:24:41 -0700 (PDT) (envelope-from kern@sibbald.com) Received: from [192.168.68.112] (rufus [192.168.68.112]) by matou.sibbald.com (8.11.6/8.11.6) with ESMTP id h7RJN3E17169; Wed, 27 Aug 2003 21:23:03 +0200 From: Kern Sibbald To: Nate Lawson In-Reply-To: <20030827110534.J31798@root.org> References: <3F4C6F55.17392.1EC66A86@localhost> <1061995529.1258.273.camel@rufus> <20030827110534.J31798@root.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-esrvvy33W9WLocWBVFPf" Organization: Message-Id: <1062012182.1227.363.camel@rufus> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 27 Aug 2003 21:23:03 +0200 cc: freebsd-scsi@freebsd.org Subject: Re: (Fwd) Re: SCSI tape data loss X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2003 19:24:44 -0000 --=-esrvvy33W9WLocWBVFPf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hello, Below is my response: On Wed, 2003-08-27 at 20:06, Nate Lawson wrote: > On Wed, 27 Aug 2003, Kern Sibbald wrote: > > Many thanks for testing this ... > > > > It seems to me that your tests, clearly indicate that > > there is a problem even though you had no data loss. > > > > When you ran without -pthread, the status > > received by the program was a 0 with 141776 > > blocks written. This is correct. > > > > When you ran with -pthread, the status > > received by the program was a -1 with 142879 > > blocks written. This is "not correct". > > > > To me, that shows very clearly that with -pthread > > the 0 status was lost and more blocks were written. > > In fact, in this case so many blocks were written > > that the tape was not properly terminated with > > an EOF (actually two EOF marks). >=20 > Here is a response I got by forwarding this to the pthreads maintainer: > > A return status of 0 from write is not interpreted as an End-Of-Tape. > > The threads library isn't smart enough to know that the file > > is a tape device and that a 0 status should break it out of the > > loop. Thus, it continues writing. Well, the threads library currently may not be smart enough to figure out that I want and need the 0 status, but I sure hope that you or someone else will figure out how to make it smarter. Best regards, Kern > > > > Use libkse :-) > > > > -- > > Dan Eischen >=20 > -Nate --=-esrvvy33W9WLocWBVFPf Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA/TQUWNgfoSvWqwEgRAhWAAKDWB/qPWlZnu1Z6T18pzeh/ySERewCg6Utc 73gODZnEoGAA43UXvWqfA7Q= =vBd5 -----END PGP SIGNATURE----- --=-esrvvy33W9WLocWBVFPf--