From: "Donald J. Barry" <don@astro.cornell.edu>
To: linux-kernel@vger.kernel.org
Subject: Write throttling problem in 2.4.2?
Date: Thu, 15 Mar 2001 19:33:24 -0500 (EST) [thread overview]
Message-ID: <200103160033.TAA09549@isc4.tn.cornell.edu> (raw)
Dear Developers:
More on my 2.4.2 oopses concerning the "Unable to handle kernel paging
request"
These only take place during ENORMOUS write pressure, and I'm curious
as to whether write throttling is an issue here. Since this is on
a reiserfs atop lvm, some of the previously conceived solutions
may not apply.
It's not a major problem, as it only occurs I can start a tars transferring
tens of gigabytes. But if I also then launch a task doing enormous activity
on the vfs, such as a simultaneous "du -s ." on the directories in
question, I can pretty reliably create the kernel paging fault.
Cheers,
Don Barry
Cornell Astronomy
-- 2.4.2 vanilla kernel + Brown's NFS patches, pretty minimal otherwise
-- problem first seen on 256M ram, still persists at 392M ram
-- LVM atop hda/hdb (60g) (motherboard via kt133 chipset) plus promise ultra66
controller driving 80 gig drive on hde
reply other threads:[~2001-03-16 0:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200103160033.TAA09549@isc4.tn.cornell.edu \
--to=don@astro.cornell.edu \
--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®