Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site mprvaxa.UUCP
Path: utzoo!linus!decvax!tektronix!uw-beaver!ubc-visi!mprvaxa!mikeg
From: mikeg@mprvaxa
Newsgroups: net.bugs.4bsd
Subject: Re: dumpdir bug
Message-ID: <258@mprvaxa.UUCP>
Date: Wed, 17-Aug-83 12:01:03 EDT
Article-I.D.: mprvaxa.258
Posted: Wed Aug 17 12:01:03 1983
Date-Received: Thu, 18-Aug-83 22:33:41 EDT
References: <1744@allegra.UUCP>
Organization: Microtel Pacific Research, Burnaby BC
Lines: 17

The bug appears in restor as well.  However, the name MAXINO is
a slighlty misleading, as the only place it is used concerns directory
inodes.  We use 9000 for restor and haven't had any problems.
To prevent core dumps whenever that limit might get exceeded, in
pass1() ipos should be checked against MAXINO.
If you decide to up MAXINO, take a look at how isearch() does it's
work -- it blindly charges on past the last used entry in inotab
checking the entire table.  It shouldn't check more than than
the first ipos entries.  Profiling shows it to be the worst offender
(one run it used 86%! forcing early exit dropped that to 6.4%)

The restor we are using it the posted version for 4.1 which will
restor entire trees by filename.

Michael Ghesquiere
Microtel Pacific Research
..!uw-beaver!ubc-vision!mprvaxa!mikeg