From: Stephen Tweedie <sct@redhat.com>
To: "Steven N. Hirsch" <shirsch@adelphia.net>
Cc: Andrew Morton <akpm@zip.com.au>,
lkml <linux-kernel@vger.kernel.org>,
"ext3-users@redhat.com" <ext3-users@redhat.com>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: ext3-0.9.15 against linux-2.4.14
Date: Wed, 7 Nov 2001 00:31:31 +0000 [thread overview]
Message-ID: <20011107003131.D7290@redhat.com> (raw)
In-Reply-To: <3BE7AB6C.97749631@zip.com.au> <Pine.LNX.4.33.0111061305540.8366-100000@atx.fast.net>
In-Reply-To: <Pine.LNX.4.33.0111061305540.8366-100000@atx.fast.net>; from shirsch@adelphia.net on Tue, Nov 06, 2001 at 01:09:42PM -0500
Hi,
On Tue, Nov 06, 2001 at 01:09:42PM -0500, Steven N. Hirsch wrote:
> > This is an incredibly obscure and hard-to-hit situation. The testcase
> > which used to trigger it can no longer do so. So if anyone sees the
> > message "try_to_swap_out: page has buffers!", please shout out.
> I have been getting thousands of these when the system was under heavy
> load, but didn't realize it was from the ext3 code! I'm using Linus's
> 2.4.14-pre7 + ext3 patch from Neil Brown's site (the latter is identified
> as "ZeroNineFourteen".) Would you like me to upgrade kernel and patch?
Andrew, the code
if (page->buffers) {
/*
* Anonymous buffercache page left behind by
* truncate.
*/
printk(__FUNCTION__ ": page has buffers!\n");
goto preserve;
}
is going to end up preserving the pte forever and shouting to syslog
every time the VM walks over the pte in question. I'd be just as
happy dropping these ptes on the floor when we find them, as they are
clearly of no use to anybody at this point.
Cheers,
Stephen
next prev parent reply other threads:[~2001-11-07 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 9:20 ext3-0.9.15 against linux-2.4.14 Andrew Morton
2001-11-06 9:42 ` Alan Cox
2001-11-06 18:09 ` Steven N. Hirsch
2001-11-06 18:49 ` Andrew Morton
2001-11-07 0:31 ` Stephen Tweedie [this message]
2001-11-07 17:59 ` Andrew Morton
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=20011107003131.D7290@redhat.com \
--to=sct@redhat.com \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shirsch@adelphia.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.