Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Apr 1998 06:30:54 +0000 (GMT)
From:      Terry Lambert <tlambert@primenet.com>
To:        chuckr@glue.umd.edu (Chuck Robey)
Cc:        syssgm@dtir.qld.gov.au, sos@FreeBSD.ORG, gmarco@giovannelli.it, current@FreeBSD.ORG
Subject:   Re: usr.bin/expand breaks make world
Message-ID:  <199804220630.XAA00982@usr06.primenet.com>
In-Reply-To: <Pine.BSF.3.96.980421094619.18524b-100000@localhost> from "Chuck Robey" at Apr 21, 98 09:48:19 am

next in thread | previous in thread | raw e-mail | index | archive | help
> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804220630.XAA00982>