Description of problem: Orphaned inodes in /tmp (80k+ at a time). Eventually causes and "out of space" error on /tmp forcing a reboot to clear. Version-Release number of selected component (if applicable): 2.1as_e25 (happens on e8 and e16 as well) How reproducible: unknown. Appears to be related to builds using Apache ant v1.5. Steps to Reproduce: 1. 2. 3. Actual results: debugfs: ncheck 256511 Inode Pathname 256511 <inode not found> debugfs: stat 256511 256511: File not found by ext2_lookup Deleted inodes on server: Under normal situations, deleted inodes should be zero. wc -l /tmp/debugfs.out 86067 /tmp/debugfs.out Filesystem Inodes IUsed IFree IUse% Mounted on /dev/cciss/c0d0p7 256512 80560 175952 32% /tmp Sample list of deleted inodes on server: Too many to list. There are about 86,000+ debugfs: Inode Owner Mode Size Blocks Time deleted 6137 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6138 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6139 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6140 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6141 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6144 783 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6145 783 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6146 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6147 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6148 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6149 783 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6150 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6151 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 6152 5704 40777 4096 1/ 1 Fri Sep 5 15:27:49 2003 Expected results: Additional info:
Is this bug still reproducible? If the bug was due to Ant rather than the Apache HTTP server then this is not the appropriate place to report the issue.
This bug is filed against RHEL2.1, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.