Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!tandem!zorch!vsi1!altos!megadon!clp
From: jdf0959@ultb.isc.rit.edu (J.D. Fulreader )
Newsgroups: comp.unix
Subject: afio
Keywords: afio, archive
Message-ID: <2247@megadon.UUCP>
Date: 3 Nov 90 02:46:17 GMT
Sender: clp@megadon.UUCP
Organization: Rochester Institute of Technology
Lines: 25
Approved: clp@megadon.UUCP
Apparently-To: uunet.uu.net!comp-unix


	In attempting to solve this problem I have observed: 

		- there is no relationship between the type of file
 		  (binary,text,etc) and the corruption of that file 

		- varying the archive block size does not seem to 
 		  improve the problem (tar uses large block size to 
		  allow it to work across a communications channel 
		  that may not maintain block size) 

		- the problem improves when the  -c buffer count  
 		  option is used(afio recommends a large count when 
	          using a streaming magnetic tape drive)

		- improvement when a wait loop is used in the remote
 		  process that sends archive data through the pipe to 
		  the local afio process

		- the problem is worse with greater load on the 
		  network


	I would appreciate any suggestions or information concerning this 
 problem.