From: Florian Lohoff <flo@rfc822.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9 / EXT3-fs warning...ext3_unlink: Deleting nonexistent file
Date: Fri, 14 Nov 2003 20:21:36 +0100 [thread overview]
Message-ID: <20031114192136.GB5594@paradigm.rfc822.org> (raw)
In-Reply-To: <20031114105724.D11847@schatzie.adilger.int>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Fri, Nov 14, 2003 at 10:57:24AM -0700, Andreas Dilger wrote:
> 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?
Nope - I have turned dir_index on on the /tmp filesystem - nowhere else.
Flo
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Heisenberg may have been here.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-14 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 17:42 Florian Lohoff
2003-11-14 17:57 ` Andreas Dilger
2003-11-14 19:21 ` Florian Lohoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031114192136.GB5594@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®