From: Eric Sandeen <sandeen@sandeen.net>
To: "Stephen C. Rigler" <srigler@marathonoil.com>
Cc: xfs@oss.sgi.com
Subject: Re: RHEL 4 Compatible Kernel Module Code
Date: Mon, 13 Nov 2006 12:09:32 -0600 [thread overview]
Message-ID: <4558B4DC.3050406@sandeen.net> (raw)
In-Reply-To: <1163434210.25484.14.camel@houuc8>
Stephen C. Rigler wrote:
> Greetings,
>
> We are using CentOS 4.4 along with the RHEL 4 compatible kernel modules
> (downloadable here:
> http://mirror.centos.org/centos/4.4/centosplus/x86_64/RPMS/).
>
> According to the CentOS mailing list, the person at SGI who had been
> backporting the xfs code for RHEL4/CentOS4 has left the company.
>
> Are there any plans to continue this work? It seems like we are getting
> bit by this bug: http://oss.sgi.com/bugzilla/show_bug.cgi?id=410 but it
> doesn't look like the fix has been backported to the RHEL4 kernel
> module.
Hot topic today; see my reply on the centos list and other recent
threads on this list :) I am planning to update the rpm package to
include some bugfixes soon, but it may not help your problems.
I had been tracking the sles9 xfs codebase as a fairly stable,
bugfix-only xfs codebase for this era of kernels; at this point I don't
-think- the extent changes you mentioned are in the sles9 codebase...
sgi guys?
It looks like you actually got a double-whammy; you probably have a very
fragmented file, which caused a large memory allocation on read, which
recursed into the filesystem, thereby blowing your stack (on x86_64!)
near as I can tell. finding & defragging the fragmented source files
may be your best bet for now. To avoid it in the future, perhaps you can
use preallocation, if you have any control over the app which is writing
these.
For those interested, the original bug report was:
http://lists.centos.org/pipermail/centos/2006-November/072221.html
-Eric
next prev parent reply other threads:[~2006-11-13 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 16:10 RHEL 4 Compatible Kernel Module Code Stephen C. Rigler
2006-11-13 18:09 ` Eric Sandeen [this message]
2006-11-14 6:42 ` Timothy Shimmin
2006-11-14 14:43 ` Eric Sandeen
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=4558B4DC.3050406@sandeen.net \
--to=sandeen@sandeen.net \
--cc=srigler@marathonoil.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox