Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!vangogh.Berkeley.EDU!casey
From: casey@vangogh.Berkeley.EDU.UUCP
Newsgroups: comp.bugs.2bsd
Subject: Re: tar "memory fault"
Message-ID: <17270@ucbvax.BERKELEY.EDU>
Date: Mon, 9-Feb-87 02:18:55 EST
Article-I.D.: ucbvax.17270
Posted: Mon Feb  9 02:18:55 1987
Date-Received: Tue, 10-Feb-87 02:34:10 EST
References: <2648@ecsvax.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: casey@vangogh.Berkeley.EDU.UUCP (Casey Leedom)
Organization: The Disposessed; Berkeley, CA
Lines: 13
Keywords: tar 2bsd bug

In article <2648@ecsvax.UUCP> khj@ecsvax.UUCP (Kenneth H. Jacker) writes:
>	We are using the 2.9BSD-CSS/Harvard system on an 11/44.  When
>"tar" is used to backup most file systems, there are no problems.
>However, another (/dev/hk1c) causes the following message to be
>displayed: "Memory fault - core dumped."

  The problem occurs because tar recursivly traverses the file system tree.
On each recursion tar uses up some ungodly amount of stack.  I will be
working on the problem when I get to porting the 4.3 tar for 2.10BSD.  In
the mean time you'll either have to use dump, or do several tars at lower
points in the file system tree.  I think tar barfs at about seven levels ...

Casey.