From: Andrew Morton <akpm@digeo.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>,
Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.56
Date: Fri, 10 Jan 2003 22:20:59 -0800 [thread overview]
Message-ID: <200301102220.59153.akpm@digeo.com> (raw)
In-Reply-To: <20030111064727.0e494512.us15@os.inf.tu-dresden.de>
On Fri January 10 2003 21:47, Udo A. Steinberg wrote:
>
> On Fri, 10 Jan 2003 12:26:56 -0800 (PST) Linus Torvalds (LT) wrote:
>
> LT> Summary of changes from v2.5.55 to v2.5.56
> LT> ============================================
>
> Hello,
>
> I just got the following bug with 2.5.56 pretty much out of the blue:
>
> VFS: brelse: Trying to free free buffer
> buffer layer error at fs/buffer.c:1182
> Call Trace:
> [<c0147105>] __brelse+0x35/0x40
Presumably one of your filesystems is using htree (indexed directories).
It's a bug - nobody has found it yet.
The modestly good news is that I have found a workload which triggers it in
ten minutes, but I have not looked into it at all.
The modestly bad news is that e2fsprogs-1.32's mke2fs enables htree by
default. It really shouldn't be doing that - htree isn't ready yet.
Use
dumpe2fs -h /dev/hda1 | grep dir_index
to see if htree is enabled.
Use
tune2fs -O '^dir_index' /dev/hda1
to disable it.
There are no trmendously bad bugs in htree. Mainly this one (which _could_
cause crashes and scribbled directories) and a small memory leak on each
unlink.
next prev parent reply other threads:[~2003-01-11 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 20:26 Linux v2.5.56 Linus Torvalds
2003-01-11 5:47 ` Udo A. Steinberg
2003-01-11 6:20 ` Andrew Morton [this message]
2003-01-11 9:43 ` Adrian Bunk
2003-01-11 9:56 ` Zwane Mwaikambo
2003-01-11 23:57 ` Dave Jones
2003-01-12 0:02 ` Dave Jones
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=200301102220.59153.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=us15@os.inf.tu-dresden.de \
/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