Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!rbj@icst-cmr.arpa
From: rbj@icst-cmr.arpa (Root Boy Jim)
Newsgroups: comp.unix.questions
Subject: Restoring to a smaller fs?
Message-ID: <11018@brl-adm.ARPA>
Date: 28 Dec 87 23:15:25 GMT
Sender: news@brl-adm.ARPA
Lines: 42


   In article <484@cos.COM> asp@COS.COM (Andrew S. Partan) writes:
   >... Guy Harris [mentioned] ... "restore" has a symbol table that it keeps
   >around in the file system it's working on; ... this symbol table can be
   >very big ... [but] there is no way to say "put that thing somewhere
   >else!".

   Ah, but there is such a way.  I had to do it once; I know it works:

At *least* one.

   First mount the file system to be restored:

	   # mount /dev/hp3a /a
	   # cd /a

   Now mount something with enough room for "restoresymtable":

	   # mount /dev/hp4a /tmp

   Finally, make a symlink from ./restoresymtable to a file in
   that second file system:

	   # ln -s /tmp/restoresymtable restoresymtable
	   # restore rf ...

   In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
   Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris

restore x creates *no* symbol table file. And no, I do not believe in
incremental restores. I do restores into separate directorys and move
the files. Deletions are easy enuf to do.

Another thing you can do is start your restore with the verbose option,
capturing the list of restored files. Suspend the restore when the file
system starts to fill, and point compress at the list of files already
restored. When space reappears, resume the restore.

	(Root Boy) Jim Cottrell	<rbj@icst-cmr.arpa>
	National Bureau of Standards
	Flamer's Hotline: (301) 975-5688
Well, O.K.  I'll compromise with my principles because of EXISTENTIAL DESPAIR!