Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.sys.ncr
Subject: Re: Huge directory
Message-ID: <70@raysnec.UUCP>
Date: 11 Sep 90 22:50:40 GMT
References: <309@gandp>
Organization: IRS/CI - Technical Solutions Branch
Lines: 21

rg@gandp (Dick Gill) writes:

>A client's 32/650 is producing a "Huge directory" message when 
>find is used to access a particular directory.  We moved some
>files elsewhere, but still get the message; there are 1401 files
>in the directory now.

Removal of a file with a standard System V filesystem does nothing to
"shrink" the size of the directory, which itself is just a special type
of file. (If you doubt this, type "od -c directoryname".)

Anything that requires a "scan" of the directory - even a simple ls -
takes longer if your directory is as large as described. This one
is so large that are forced to access "indirect" blocks associated 
with the directory file.

Suggest you spend some time reorganizing your resources, then run the
public domain 'sqzdir' utility to squeeze the empty slots out of the
cleaned out directories. It should be portable to the NCR.

						shwake@rsxtech