Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 2/6/85; site rocksvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!rocksvax!z
From: z@rocksvax.UUCP (Jim Ziobro)
Newsgroups: net.news.notes
Subject: detecting problems with notesfile
Message-ID: <1445@rocksvax.UUCP>
Date: Wed, 18-Sep-85 20:37:56 EDT
Article-I.D.: rocksvax.1445
Posted: Wed Sep 18 20:37:56 1985
Date-Received: Fri, 20-Sep-85 04:25:48 EDT
Organization: Xerox: Henrietta, NY
Lines: 29

We have been having some problems with notesfiles being corrupted.  When
this happens the daily nfarchive job dies and any notesfile after the
corrupted one never get expired.  A few days of this will result in an
overflow of the disk.  I would suggest everyone add a line to their
system startup file:

ls -l /usr/spool/notes/.locks			>/dev/console

This will tell of problems at least at startup.

In the meantime I am trying to locate the source of the corruption.  Our
version:
main.c:
$Header: main.c,v 1.5 84/04/08 01:20:25 salkind Exp $

It appears the response chain gets corrupted.  At least this is what debbugging
the compress routine shows.  What is strange though is that the notesfile
seems to still be readable!  This has been hitting us about once/week.  This
seemed to have started after I increased the expiration time to 19 days.
I have the suspision that it has something to do with the strange way notes
handles greater than 25 responses to a base note.  Simply creating a test
notesfile with >25 responses doesn't bring out the problem.  Help!?!?

Do I have the latest version?  Lou are you listening?
-- 
//Z\\
James M. Ziobro
Ziobro.Henr@Xerox.ARPA
{rochester,amd,sunybcs,allegra}!rocksvax!z