Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!pur-ee!uiucdcs!uiucdcsb!acheng From: acheng@uiucdcsb.cs.uiuc.edu Newsgroups: comp.unix.questions Subject: Re: Restoring to a smaller fs? Message-ID: <166400006@uiucdcsb> Date: Fri, 23-Oct-87 03:14:00 EST Article-I.D.: uiucdcsb.166400006 Posted: Fri Oct 23 03:14:00 1987 Date-Received: Sun, 25-Oct-87 15:39:43 EST References: <482@cos.COM> Lines: 37 Nf-ID: #R:cos.COM:482:uiucdcsb:166400006:000:1495 Nf-From: uiucdcsb.cs.uiuc.edu!acheng Oct 23 02:14:00 1987 >/* Written 1:18 pm Oct 21, 1987 by asp@COS.COM in uiucdcsb:comp.unix.questions */ >I think that Guy Harris said it best: > > One problem is that "restore" has a symbol table that it keeps > around in the file system it's working on;... > > Unfortunately, this symbol table can be very big, which means > you need enough space on the partition for all the files *and* > for the symbol table. (The astute reader will note that this > can make it impossible to restore a full dump of a partition > back onto that partition after re-"newfs"ing that partition.) > Unfortunately, there is no way to say "put that thing somewhere > else!". If Guy Harris really said that, do I have something to surprise him. Use a symbolic pointer to bypass it. E.g. if you are restoring a full /a: cd /a ln -s /tmp/restoresymtable restoresymtable # make sure /tmp/restoresymtable does not exist or is 0 byte. restore r The restoresymtable grows in /tmp, not /a. (This works in my 4.3BSD VAX system and I imagine it will in others) If your old system was absolutely full that not even a symbolic pointer could fit, remove lost+found after restore has started. It is usually empty. But this I have not tested. ---------------------------------------------------------------------- Albert Cheng acheng@a.cs.uiuc.edu (ARPAnet or CSNET) uiucdcs!acheng(USENET) Dept. of Computer Science, Univ. of Illinois-Urbana, Rm. 240, 1304 W. Springfield, Urbana, IL 61801, USA. %%% The above is my opinion STOP %%%