From owner-freebsd-current Tue Apr 21 23:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29419 for freebsd-current-outgoing; Tue, 21 Apr 1998 23:32:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29254; Wed, 22 Apr 1998 06:31:16 GMT (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id XAA07069; Tue, 21 Apr 1998 23:31:03 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd007051; Tue Apr 21 23:30:55 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA00982; Tue, 21 Apr 1998 23:30:55 -0700 (MST) From: Terry Lambert Message-Id: <199804220630.XAA00982@usr06.primenet.com> Subject: Re: usr.bin/expand breaks make world To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 22 Apr 1998 06:30:54 +0000 (GMT) Cc: syssgm@dtir.qld.gov.au, sos@FreeBSD.ORG, gmarco@giovannelli.it, current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Apr 21, 98 09:48:19 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wonder if my recent disk problem (the only one I've ever had with > FreeBSD, where I had directories entries being inserted into dirs, with > the inode set as 0) could be this? I was doing buildworld with -j 12 on > an SMP machine. Inode of 0 is a deleted file indicator, if the file being deleted is the first entry in the directory block. If the file is not the first entry in the block, then the previous entry makrs the next entry past it as being the next entry -- and you don't need t zero the inode. My personal preference would be a "deleted" flag (to which I would add a "purded" flag, so that I could have an "undelete" program). Ah well, I'm rarely consulted on such things. In any case, if the inode number was the first entry in a directory block, then this was the "problem"... ie: it wasn't broken. If the inode number was in a non-initial directory entry, well then you have a problem. If only the inode was zero, but the file name was not, this can not be a VM access problem, since directory blocks are on 512b boundries and pages (the smallest VM increment) are on 4K boundries -- or are really, really big). Instead, it would have to be indicative of a different (not NFS related) problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message