tar 1.10 bug with big files, multi-volume update

Thread View: gnu.utils.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by brian Mon, 23 Nov 1992 22:32

#1138

Author: brian
Date: Mon, 23 Nov 1992 22:32

34 lines
1681 bytes

Hey there,

	I sent a bug report last week regarding tar v1.10 and large
files across multivolumes.  Well I have some more information.

	I put in some debug statements to find the values of various
variables while the archive was being created.  The results are
interesting.  When creating the archive, I got the following
values when changing tapes...

real_s_totsize=5169664, real_s_sizeleft=2402304, head->header.offset=   12235000 

so it appears that there is not an error with creating the header.offset
value as I originally suspected.  Here are the same variables when the 
archive was read back...

real_s_totsize=5169664, real_s_sizeleft=2467840, ar_block->header.offset=   1223
5000

the value of real_s_sizeleft is 65536 bigger when reading that it was when
writing.  Why would this be??

What is real_s_sizeleft??  I suspect it is the number of bytes left to read
to make the current file complete.

any ideas??

brian

-- 
Brian J. Murrell                                        brian@ilinx.wimsey.bc.ca
InterLinx Support Services, Inc.                        uunet!van-bc!ilinx!brian
North Vancouver, B.C.
        Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads