From: "Kevin P. Fleming" <kpfleming@cox.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "Rechenberg, Andrew" <ARechenberg@shermanfinancialgroup.com>,
linux-kernel@vger.kernel.org
Subject: Re: OOPS in do_try_to_free_pages with VERY large software RAID array
Date: Mon, 10 Mar 2003 12:48:16 -0700 [thread overview]
Message-ID: <3E6CEC00.4030707@cox.net> (raw)
In-Reply-To: <6240000.1047324468@flay>
Martin J. Bligh wrote:
> At a wild guess (OK, I only looked for about 1 minute),
> md_status_read_proc is generating more than 4K of information, and overwriting
> the end of it's 4K page. Throw some debug in there, and get it to printk
> how much of the buffer it thinks it's using (just printk sz every time it
> changes it). If it's > 4K, convert it to the seq_file interface.
>
> May not be it, but it seems likely given the unusual scale of what you're
> doing, and it's easy to check.
>
> M.
I posted a patch to do exactly this last week to the Linux-RAID mailing list. If
you check the archives you should find it. This problem also occurs if you use
the device-mapper under 2.5.X, because it makes all 256 md minors appear in the
tables and /proc/mdstat wants to tell you about all of them.
next prev parent reply other threads:[~2003-03-10 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 19:20 OOPS in do_try_to_free_pages with VERY large software RAID array Rechenberg, Andrew
2003-03-10 19:27 ` Martin J. Bligh
2003-03-10 19:48 ` Kevin P. Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 20:18 Rechenberg, Andrew
2003-03-11 19:38 Rechenberg, Andrew
2003-03-11 19:39 ` Martin J. Bligh
2003-03-11 17:38 Rechenberg, Andrew
2003-03-11 17:49 ` Randy.Dunlap
2003-03-10 21:23 Rechenberg, Andrew
2003-03-10 21:52 ` Martin J. Bligh
2003-03-10 19:19 Rechenberg, Andrew
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=3E6CEC00.4030707@cox.net \
--to=kpfleming@cox.net \
--cc=ARechenberg@shermanfinancialgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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.