Hi,

I'm trying to restore a 200g file system after a disk failure.
The restore seems to go along for a while, but then I get this
message in the bp.log.rest file:


16:39:54 (408411.001) read error on -: Connection reset by peer
16:39:54 (408411.001) archive - EOF not on block boundary
16:39:54 (408411.001) INF - TAR EXITING WITH STATUS = 3

The times I've seen block boundary errors in non-nbu arena,
it's had something to do with a corrupt tar file, or *.gz
file. Can anyone clue me in as to a workaround? Right now
I'm restarting the restore from where it craps out, but
that seems to be a long haul for this big of a partition.

Both server and client are Solaris8, running NBU4.5mp5.
Tape drives are 9940s.

Thanks,

Gregg
=================================================================
Gregg MacKinnon                         Ford Motor Co.
gmackinn AT ford DOT com                        2101 Village Rd.
Technical Computing Section             Rm 1116, MD 1076        
(313) 594-3716   pager 7958343          Dearborn Michigan, 48124
==================================================================