Bug 60989

Summary: "Ext3 warning: deleting non-existent file" error during newburn
Product: [Retired] Red Hat Linux Reporter: Clay Cooper <clay_cooper>
Component: kernelAssignee: Stephen Tweedie <sct>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: afom_m, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, joshua_giles, matt_domsch, michael_e_brown, robert_hentosh, rogelio_noriega
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-03-27 17:40:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 61590    
Attachments:
Description Flags
Dmesg file from newburn log directory
none
Syslog file from newburn log directory none

Description Clay Cooper 2002-03-11 16:21:53 UTC 
Description of Problem:  On a beetle running hampton beta2 (2.4.18-0.1) w/ bios
A04, 2GB ram, and 2GB swap.  While running newburn, Dmesg and Syslog files in
newburn log directory report multiple errors stating:

"EXT3-fs warning (device sd(8,3)): ext3_unlink: Deleting nonexistent file
(2703621), 0"

Attaching DMESG and SYSLOG files from newburn log directory


Version-Release number of selected component (if applicable):


How Reproducible:  Everytime


Steps to Reproduce:
1. Install hampton beta2 on a beetle
2. Run newburn
3. Note dmesg and syslog errors.  Check newburn logs

Actual Results:


Expected Results:


Additional Information:
Comment 1 Clay Cooper 2002-03-11 16:22:27 UTC 
Created attachment 48144 [details]
Dmesg file from newburn log directory
Comment 2 Clay Cooper 2002-03-11 16:23:23 UTC 
Created attachment 48145 [details]
Syslog file from newburn log directory
Comment 3 Stephen Tweedie 2002-03-26 22:36:23 UTC 
Is this reproducible?  Are there any other kernel messages in the logs?
Comment 4 Stephen Tweedie 2002-03-27 17:07:09 UTC 
Are there any other signs of problems?  This particular error means that we are
deleting an inode but its "nlinks" --- the number of directory entries pointing
to it --- is already zero.  You have a bunch of those in sequence:

EXT3-fs warning (device sd(8,3)): ext3_unlink: Deleting nonexistent file
(2703617), 0
EXT3-fs warning (device sd(8,3)): ext3_unlink: Deleting nonexistent file
(2703621), 0
EXT3-fs warning (device sd(8,3)): ext3_unlink: Deleting nonexistent file
(2703622), 0
EXT3-fs warning (device sd(8,3)): ext3_unlink: Deleting nonexistent file
(2703623), 0

and that could indicate many possible things, including on-disk corruption of a
single inode block affecting multiple files (ie. it could be a driver or disk
fault as easily as a filesystem one, or a higher-layer VFS locking problem.)
Comment 5 Clay Cooper 2002-03-27 17:40:05 UTC 
Tried to reproduce this in hampton beta3 by running newburn and did not see it
before newburn oopsed at 22 hours.  Once newburn runs without oopsing at all I
will try to reproduce this again.
Comment 6 Stephen Tweedie 2002-03-27 18:08:05 UTC 
OK, let's leave this to once side for now, until we know why we're oopsing.