From: Chris Mason <mason@suse.com>
To: Blizbor <tb670725@ima.pl>, reiserfs-list@namesys.com
Cc: reiser@idiom.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] VFS: brelse message in syslog, its due to ReiserFS or kernel failure ?
Date: Tue, 28 Nov 2000 11:26:54 -0500 [thread overview]
Message-ID: <120880000.975428814@coffee> (raw)
In-Reply-To: <5.0.0.25.0.20001128142121.01da9e20@195.117.13.2>
On Tuesday, November 28, 2000 14:29:34 +0100 Blizbor <tb670725@ima.pl>
wrote:
> Machine: P3 500 on ASUS P2B, WD 15GB IDE drive.
> System RH7 with upgraded glibc.
>
> When I'm using 2.2.17 with ReiserFS:
> Nov 26 00:05:05 localhost kernel: Linux version 2.2.17
> (root@localhost.localdomain) (gcc version egcs-2.91.66 19990314/Linux
> (egcs-1.1.2 relea se)) #9 Sat Nov 25 17:09:40 CET 2000
>
> I have such messages in syslog and console:
> Nov 26 06:00:49 localhost kernel: VFS: brelse: Trying to free free buffer
> Nov 26 06:07:41 localhost kernel: VFS: brelse: Trying to free free buffer
> Nov 26 06:32:28 localhost kernel: VFS: brelse: Trying to free free buffer
>
> FS size is about 8GB.
>
> When I've switched to 2.4.0-test11 + ReiserFS patch there are no such
> messages.
>
> Both kerlels are patched with latest ReiserFS patches.
These messages could have been caused by a journal bug I fixed a few weeks
ago. The patch is in the reiserfs mailing list archives, I'll send it to
you privately.
Hans, could we please put out a 3.5.28 from the code in CVS?
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-28 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 13:29 VFS: brelse message in syslog, its due to ReiserFS or kernel failure ? Blizbor
2000-11-28 14:29 ` VFS: brelse message in syslog, its due to ReiserFS or kernelfailure ? David Ford
2000-11-28 16:26 ` Chris Mason [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=120880000.975428814@coffee \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@idiom.com \
--cc=reiserfs-list@namesys.com \
--cc=tb670725@ima.pl \
/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