xfs
[Top] [All Lists]

Re: Are there mmap problems with xfs 2.4.17?

To: Eric Sandeen <sandeen@xxxxxxx>
Subject: Re: Are there mmap problems with xfs 2.4.17?
From: Jason White <jasonw@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 17 Aug 2002 10:56:36 +1000
Cc: linux-xfs <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.44.0208152241390.1311-100000@xxxxxxxxxxxxxxxxxxxxxx>
References: <15708.22618.786062.458402@xxxxxxxxx> <Pine.LNX.4.44.0208152241390.1311-100000@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: jasonw@xxxxxxxxxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Eric Sandeen writes:
 > On Fri, 16 Aug 2002, Jason White wrote:
 > 
 > > The kernel I am running is:
 > > Linux jdc 2.4.17-xfs #1 Sat Jan 19 16:47:16 EST 2002 i686
 > > (checked out from cvs on that date).
 > >
 > > Any suggestions?
 > 
 > Hi Jason - Yes, my suggestion would be to please upgrade your kernel
 > and see if it goes away.
I upgraded and the problem appears to have gone - probably the 2.4.17
 > mmap issue. After a few further crashes and db_recover operations,
 > whatever corruption was in the Berkeley db databases was,
 > presumably, cleaned away; and I haven't experienced any failures since.
 > I understand that you may not want to bring
 > your system to 2.4.19 yet, but the XFS that was in 2.4.17
 > in the paleolithic days of Jan 2001 is quite different from the code
 > in CVS today.  If you can boot it up for a trial, it would be very
 > helpful, as we really aren't able to go back to debug 9 month old
 > code.

That's fine. I am one of those who would defend the developers' policy
of only supporting the latest code (except perhaps for customers who
take out service contracts, but that's a different issue).

Thank you for your help and with apologies for adding unnecessary traffic to the
list.


<Prev in Thread] Current Thread [Next in Thread>