xfs
[Top] [All Lists]

Re: xfs oops (CVS-2004-05-15_05:00_UTC)

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: xfs oops (CVS-2004-05-15_05:00_UTC)
From: Krzysztof Rusocki <kszysiu@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 24 Jun 2004 13:46:08 +0200
Cc: linux-xfs@xxxxxxxxxxx, hch@xxxxxxxxxxxxx
In-reply-to: <20040624024320.GB5866@frodo>
References: <20040604130816.GA12556@xxxxxxxxxxxxxxxxxxxx> <20040621010330.GA1295@xxxxxxxxxxxxxxxxxxxx> <20040621021505.GA1173@frodo> <20040621025905.GA1323@xxxxxxxxxxxxxxxxxxxx> <20040621072906.GD1656@frodo> <20040622082906.GA2093@frodo> <20040623084922.GD1323@xxxxxxxxxxxxxxxxxxxx> <20040623203639.A1670881@xxxxxxxxxxxxxxxxxxxxxxxx> <20040623131611.GE1323@xxxxxxxxxxxxxxxxxxxx> <20040624024320.GB5866@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
> > 
> > It seems that changes included in 1.1371.750.18 may be responsible
> > for discussed behavior. Machine's been running without problems
> > for over 5 hours now. I'll stress it more and let know whether
> > this state is persistent.
> 
> Ah - thanks, I'll study that change and get back to you.
> 

Okay, I've run even more tests yesterday and during the night, conclusions:

- current CVS without 1.1371.750.18 - oops in ... minutes
- current CVS without undelay changes
  (xfs_buf.c 1.171, xfs_buf.h 1.97) - minutes.. aswell
- current CVS without 1.1371.750.18 _and_ undelay changes - no problems
  (tested 10 hours)
- current CVS without 1.1371.750.18, 1.1587.5.6 1.1722.10.100 and undelay
  changes - no problems (tested 14 hours)

HTH,

Krzysztof


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