[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: the files listed with du -a do not match ls -R, possible bug?

From: Bob Proulx
Subject: Re: the files listed with du -a do not match ls -R, possible bug?
Date: Sat, 17 Aug 2002 11:51:54 -0600
User-agent: Mutt/1.4i

Aaron Wegner <address@hidden> [2002-08-15 13:59:06 -0500]:
> I think I found what may be a bug in the du program.  So far I have
> only been able to observe this anomaly in my build directory for
> glibc.

I as well was unable to recreate your problem in any of the
directories that I had lying around.  BTW that was a good job of
presenting a small test case of commands that would recreate the
problem.  However the data set is not readily available so more help
is needed.

> The bug is uncovered with the following commands, issued
> from the base of the [glibc] build directory:
> --------------------------------------
> # ls -lR | grep '\.op$' | awk '{printf("%s\n", $NF)}' | sort > ls_c_files
> # du -a . | grep '\.op$' | awk 'BEGIN {FS="[\/]"} {printf("%s\n", $NF)}' | 
> sort > du_c_files
> # sdiff -s du_c_files ls_c_files
>                                                               > mcount.op
>                                                               > profil.op
>                                                               > sprofil.op
> ---------------------------------------

What types of files are those *.op files?

  ls -ld *.op

I am guessing they are not normal files.  Probably dangling symlinks
or sockets or some such.  But it would be a clue as to why those files
were not seen by 'du -s'.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]