From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: xfs@oss.sgi.com
Cc: nscott@aconex.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: New CentOS4/RHEL4-compatible xfs module rpms
Date: Thu, 07 Dec 2006 16:35:35 -0500 [thread overview]
Message-ID: <45788927.4030207@falconstor.com> (raw)
In-Reply-To: <1165525906.30459.25.camel@edge>
Nathan Scott wrote:
> Does it happen with mainline (current) kernels? This is ringing some
> distant bells, something to do with an atomic_inc being in the wrong
> spot in [_]xfs_trans_alloc ... or maybe a wrong call to xfs_trans_alloc
> instead of the '_' prefixed version - details are murky now though. I
> do remember fixing ... something in here, a few months back, that fix
> may not be in Eric's codebase yet.
>
> cheers.
I've only tried this on RHELAS4 with the kernel shipped with Update 2. I
have not tried to update the kernel, or install Update 4 or whatever is
current now. My kernel is 2.6.9-22.ELsmp.
It wouldn't be easy for me to switch to a newer kernel, because it is
not just a matter of my machine --we have a product built for this
particular configuration. Switching to a new kernel would reset our QA
efforts.
If this may be fixed in the XFS modules on the other hand, then it would
be awesome if we could get it resolved with an updated XFS package for
RHEL4. I would be more than willing to put in an extra effort and work
with anyone on this.
--
Geir A. Myrestrand
next prev parent reply other threads:[~2006-12-07 21:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 19:07 New CentOS4/RHEL4-compatible xfs module rpms Eric Sandeen
2006-12-07 17:25 ` Geir A. Myrestrand
2006-12-07 17:52 ` Eric Sandeen
2006-12-07 18:17 ` Geir A. Myrestrand
2006-12-07 23:26 ` David Chinner
2006-12-08 2:58 ` Geir A. Myrestrand
2006-12-07 18:19 ` Geir A. Myrestrand
2006-12-07 20:51 ` Geir A. Myrestrand
2006-12-07 21:11 ` Nathan Scott
2006-12-07 21:35 ` Geir A. Myrestrand [this message]
2006-12-07 21:40 ` Nathan Scott
2006-12-07 21:51 ` Geir A. Myrestrand
2006-12-07 22:06 ` Nathan Scott
2006-12-07 22:16 ` Geir A. Myrestrand
2006-12-07 22:18 ` Eric Sandeen
2006-12-07 22:25 ` Geir A. Myrestrand
2006-12-07 22:30 ` Eric Sandeen
2006-12-07 22:52 ` Geir A. Myrestrand
2006-12-07 22:53 ` Eric Sandeen
2006-12-07 23:08 ` Geir A. Myrestrand
2007-07-19 14:37 ` James Braid
2007-07-19 15:15 ` Eric Sandeen
2007-07-21 3:34 ` James Braid
2007-07-21 14:58 ` Eric Sandeen
2007-07-21 15:36 ` James Braid
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:04 James Pearson
2007-08-08 16:09 ` 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=45788927.4030207@falconstor.com \
--to=geir.myrestrand@falconstor.com \
--cc=nscott@aconex.com \
--cc=sandeen@sandeen.net \
--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