Message-ID: <3D1DDC5E.1010403@mountainviewdata.com>
Date: Sun, 30 Jun 2002 00:12:14 +0800
From: Eric Mei <eric@mountainviewdata.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
MIME-Version: 1.0
To: linux-xfs@oss.sgi.com
Subject: Re: Bug about XFS-1.0.1 on 2.4.5
References: <3D1D647F.3070302@mountainviewdata.com> <1025365517.20112.18.camel@Liberator>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

Thanks a lot!

As you know, if we try to backport vm fixes to 2.4.5, which kernel have
most probably addressed this issue? 2.4.7? There is no evidence about it
from kenrel ChangeLog.

Sorry to occupy XFS's bandwidth again :-)


Eric Sandeen wrote:
> On Sat, 2002-06-29 at 03:40, Eric Mei wrote:
> 
>>Hi Team,
>>
>>This is a long report. I know some of you might be busy on kernel
>>summit, we just can's believe XFS has such a serious bug. 
> 
> 
> s/has/had/
> 
> 
>>For some reason, we must stick on 2.4.5-xfs-1.0.1.
> 
> 
> You're essentially saying that you must stick with old, (apparently)
> buggy code.  We simply don't have the bandwidth to support xfs & kernel
> code from 1 year ago.
> 
> Your best bet would be to look through the mailing list archives to see
> if anyone has had a similar problem, and see if a mod was checked in to
> fix it; then try to backport that fix.
> 
> http://oss.sgi.com/projects/xfs/mail_archive/200108/msg00307.html
> 
> This thread makes it sound like it may well be an underlying kernel
> problem with 2.4.5-era kernels.
> 
> -Eric