Originally posted by: tony.evans
Well the permissions on /usr do look a little scary, you should consider how they got that way.
There is a less sinister reason for a filesystem continuing to fill up despite find not locating the cause - files which were open and removed, and are still in use. For example, if an application is logging output to a file and the file is open, and someone removes the file with rm (to do some housekeeping), the application will continue writing to the file handle it had, and AIX will continue sticking data into the filesystem, but you won't be able to see where it's going.
This can explain the difference between a df showing a 100% full filesystem and a du -sm showing insufficient files to fill a filesystem.
You could use fuser (or lsoff) to see if any processes still believe they're writing to /usr, you could check /usr with fsck in read only mode and see if it believes there's some corruption or inode confusion.
You'll need to learn how to read man pages as well. man find will tell you how to use find to locate files changed in the last few days just to make sure. Try,
find /usr -xdev -mtime -5 -ls