(Fwd) Re: SCSI tape data loss
Kern Sibbald
kern at sibbald.com
Wed Aug 27 12:24:44 PDT 2003
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).
>
> 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
>
> -Nate
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20030827/c03e9264/attachment.bin
More information about the freebsd-scsi
mailing list