Re: du: fts and vfat

[Jim Meyering]

Justin Pryzby <address@hidden> wrote:
> However this time the problem occurred only on the first invocation.
> $ du -sh /mnt/1/music/jake/
> du: `/mnt/1/music/jake/Music/Newly Ripped': No such file or directory
...
> 186G    /mnt/1/music/jake/
>
> I note that yesterday I added a 2nd 128MB ram chip to this machine.
> So my current hypothesis is that there's a hash table or such of
> inodes which was being overflowed.  So this may just be an (expected?)
> consequence of accessing a large devices (with many files) on a
> machine with not much ram.

Yes, it's expected, whenever you use a file system with
imperfect-by-definition inode emulation.

If you use coreutils-6.9 instead, this should be mitigated,
since in the newer version of fts.c, the temporal locality of inode
use and reuse is more cache friendly.