|Subject:||Re: New CentOS4/RHEL4-compatible xfs module rpms|
|From:||"Geir A. Myrestrand" <geir.myrestrand@xxxxxxxxxxxxxx>|
|Date:||Thu, 07 Dec 2006 16:35:35 -0500|
|Cc:||nscott@xxxxxxxxxx, Eric Sandeen <sandeen@xxxxxxxxxxx>|
|Organization:||FalconStor Software, Inc.|
|References:||<4560AB84.email@example.com> <45784E71.firstname.lastname@example.org> <457854CB.email@example.com> <45787ED4.firstname.lastname@example.org> <1165525906.30459.25.camel@edge>|
|User-agent:||Thunderbird 22.214.171.124 (Windows/20061025)|
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.
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
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: New CentOS4/RHEL4-compatible xfs module rpms, Nathan Scott|
|Next by Date:||Re: New CentOS4/RHEL4-compatible xfs module rpms, Nathan Scott|
|Previous by Thread:||Re: New CentOS4/RHEL4-compatible xfs module rpms, Nathan Scott|
|Next by Thread:||Re: New CentOS4/RHEL4-compatible xfs module rpms, Nathan Scott|
|Indexes:||[Date] [Thread] [Top] [All Lists]|