From owner-freebsd-questions  Tue May 13 14:40:01 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA16742
          for questions-outgoing; Tue, 13 May 1997 14:40:01 -0700 (PDT)
Received: from train.tgci.com ([205.185.169.3])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA16715
          for <questions@FreeBSD.ORG>; Tue, 13 May 1997 14:39:58 -0700 (PDT)
Received: from emilyd ([206.250.85.68]) by train.tgci.com (8.6.12/8.6.9) with SMTP id PAA04665; Tue, 13 May 1997 15:06:52 -0700
Message-Id: <199705132206.PAA04665@train.tgci.com>
Comments: Authenticated sender is <chaos@mail.tgci.com>
From: "Riley J. McIntire" <chaos@mail.tgci.com>
To: Alec Kloss <alec@d2si.com>
Date: Tue, 13 May 1997 14:38:49 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: (Fwd) (Fwd) File descriptors-do I have Bad Breath?
Reply-to: chaos@tgci.com
CC: questions@FreeBSD.ORG
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.42a)
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> From:          Alec Kloss <alec@d2si.com>
> Subject:       Re: (Fwd) (Fwd) File descriptors-do I have Bad Breath?
> To:            chaos@tgci.com
> Date:          Tue, 13 May 1997 14:39:09 -0500 (CDT)

> Riley J. McIntire is responsible for:
>                         [stuff deleted]
> > Thanks Alec, it has helped!
> No problem.
> > 
> > > > 
> > > > find: /usr/include/machine: Bad file descriptor
> > > > find: /usr/src/gnu/usr.bin/cc/cc_int/loop.c: Bad file descriptor
> > > > find: /usr/src/gnu/usr.bin/cc/cc_int/obstack.c: Bad file descriptor
> > > > etc
> > 
> > But why would this show up in syslog?  From what I'm getting these 
> > should have disappeared after the failed kernal compile?  Assuming no 
> > other process is accessing them.  And fsck doesn't help.
> 
> Are you saying that these errors from find are showing up in
> /var/log/messages, not while you are running find yourself?  If so,
> I've got a theory, but looking into the source for find I don't know
> if I could prove it.  My theory is that, periodically, if you system
> is like mine, it runs a script 
>         /usr/libexec/locate.updatedb
> which updates the database the locate(1) program uses.
> locate.updatedb(8) is a bourne shell script that uses the find(1)
> program to scan your filesystem, archiving names of the files it
> finds.  This may be why messages from find are showing up unprovoked.
> It's just a theory though.
> 
That makes sense.  The above shows up in the security log output in 
my email, and (I'm still in the middle of upgrading) I suppose in 
/var/log/messages--I haven't checked.

But it appeared after the failed kernal compile.  And it looks like 
and acts (with fsck) like some "bad file descriptors" messages I got 
about files in lost+found about a month ago.  fsck wouldn't fix 'em, 
I couldn't delete them, and to get rid of 'em I had to clri (clear 
inodes) individually and then fsck them.

Something seems to be damaging the files, and then this message 
appears.  And from what you tell me it doesn't really look like a bad 
disk should generate this type of message.

Anyway, assuming the upgrade goes ok I'll do more testing  on the 
disk for physical damage.

Ciao,

Riley