Date: Fri, 14 Nov 2003 10:57:24 -0700
From: Andreas Dilger <adilger@clusterfs.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 / EXT3-fs warning...ext3_unlink: Deleting nonexistent file
Message-ID: <20031114105724.D11847@schatzie.adilger.int>
Mail-Followup-To: Florian Lohoff <flo@rfc822.org>,
	linux-kernel@vger.kernel.org
References: <20031114174254.GA5594@paradigm.rfc822.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20031114174254.GA5594@paradigm.rfc822.org>; from flo@rfc822.org on Fri, Nov 14, 2003 at 06:42:54PM +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1202
Lines: 28

On Nov 14, 2003  18:42 +0100, Florian Lohoff wrote:
> i seem to have experienced some ext3 inconsistencys - After some reboots
> today i was wondering why cron wasnt running and discovered that
> starting cron failed because /var/run/crond.pid could not be written.
> ls did not show and file under that name. touch showed i/o error on that
> file although other file in that directory could be touched.
> 
> When i tried to rm crond.pid this showed up:
> 
> EXT3-fs warning (device hda8): ext3_unlink: Deleting nonexistent file (107669), 0
> 
> After that i could touch the file again and crond did not refuse to start anymore.

This sounds like the htree "get back deleted entry on directory split" bug
that was fixed months ago in 2.6 htree, but not in any 2.4 patches.  Did
you test htree on this system under 2.4 recently?

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/