Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari!caesar.cs.montana.edu!ogicse!unicorn!csispt!bob
From: bob@csispt.UUCP (Bob Finch)
Newsgroups: news.software.nn
Subject: Re: Less than meets the eye
Keywords: nn
Message-ID: <1990Feb24.070659.608@csispt.UUCP>
Date: 24 Feb 90 07:06:59 GMT
References: <4075@paperboy.OSF.ORG> <4078@paperboy.OSF.ORG>
Organization: AlphaSoft, Bellingham, WA
Lines: 22

hankin@sauron.osf.org (Scott Hankin) writes:
>    The final straw!  Doing a reinit of the entire  database (an admittedly
>    tiresome and time  consuming activity)  does  NOT restore these  zeroed
>    data  files!   They must be  recollected individually  to restore  them
>    completely.

About four weeks ago I encountered what sounds like the same problem
after upgrading from 6.3.1 to 6.3.10.  After initializing the entire
database, about 10% of the data files were 0 length.  Initializing
again resulted in about the same number of 0 length data files, but in
different groups.

I spent about a day tracing through initializing the database in
nnmaster with sdb, but I never caught it zeroing a data file.  Since
then, nnmaster has run without problems.

I never found what caused the problem, and why it did not occur while
running nnmaster under sdb. I suspect, however, that if I tried to
reinitialize the database, the problems would reoccur.

-- Bob Finch      bob%csispt.UUCP@unicorn.wwu.edu
   AlphaSoft      +1 (206) 671-6214