Chris Wedgwood wrote: > > On Mon, Aug 06, 2001 at 02:40:43PM -0700, Gregory S. Youngblood > wrote: > > The problem is that ls -U (for unsorted list), or just place ls or > du, on this specific directory does not return anything and just > thrashes the hard drive ( and CPU to a lesser degree ). I left ls > running for between 60 and 90 minutes before killing it. The > directory listing from the Windows box never returned either. > > strace'ing ls reveals it wants read all the dirents before displaying > anything --- with that many files, it probably will take a long time > to read them all... > > How much ram does the box have? Might there be so much metadata it > just doesn't fint into RAM? (I've tested to 120,000 files without any > real problems, but no more). > > --cw I would guess that Chris is right about this. Hans
