From: Kelledin Tane <runesong@earthlink.net>
To: baggins@sith.mimuw.edu.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why can't I flush /dev/ram0?
Date: Mon, 18 Jun 2001 20:37:29 -0500 [thread overview]
Message-ID: <3B2EACD9.D1D2B90A@earthlink.net> (raw)
In-Reply-To: <3B2E6EA3.3DED7D95@earthlink.net> <20010618235537.B17458@sith.mimuw.edu.pl>
> > When I mount the filesystem to check it out, nothing appears to have
> > anything open on the filesystem. So why am I not able to flush it
> > clean?
>
> Because of a bug present in Linus tree. Try this patch:
Thanks, that seems to have fixed it. There's something else I'm curious about
though...
Before, when I was having this problem, I would check mem usage, and there would
be about 5MB of physical memory marked for "buffers" (I assume 4MB for ram0).
Now, using an identical kernel configuration, an identical module set loaded,
and a roughly identical process table, there's about 18MB of memory marked for
"buffers!"
Sorry to be a bother, but I can't help wondering if this patch might have gotten
rid of one problem and replaced it with another? Or maybe I'm missing some
other detail here...
Kelledin
bash-2.05 $ kill -9 1
init: Just what do you think you're doing, Dave?
next prev parent reply other threads:[~2001-06-19 1:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 21:12 Why can't I flush /dev/ram0? Kelledin Tane
2001-06-18 21:23 ` Richard B. Johnson
2001-06-18 21:41 ` Kelledin Tane
2001-06-18 21:55 ` Jan Rekorajski
2001-06-19 1:37 ` Kelledin Tane [this message]
2001-06-19 2:58 ` Linux 2.4.6-pre3 breaks ReiserFS mount on boot Shawn Starr
2001-06-19 3:14 ` Olivier Galibert
2001-06-19 3:23 ` Shawn Starr
2001-06-19 3:57 ` Shawn Starr
2001-06-19 4:59 ` Chris Mason
2001-06-19 5:06 ` Jeff Mahoney
2001-06-19 5:31 ` Neil Brown
2001-06-19 5:37 ` Jeff Mahoney
2001-06-25 13:40 ` Shawn Starr
2001-06-19 8:12 ` Justin Guyett
2001-06-19 9:33 ` Alan Cox
2001-06-19 15:13 ` Chris Mason
2001-06-19 15:35 ` David Ford
2001-06-19 3:32 ` Chris Mason
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=3B2EACD9.D1D2B90A@earthlink.net \
--to=runesong@earthlink.net \
--cc=baggins@sith.mimuw.edu.pl \
--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