On Wed, Jul 02, 2008 at 09:48:46AM +0530, Sagar Borikar wrote:
> Dave Chinner wrote:
>> On Mon, Jun 30, 2008 at 03:54:44PM +0530, Sagar Borikar wrote:
>> Sure - just like any other workload that generates enough
>> extents. Like I said originally, we've fixed so many problems
>> in this code since 2.6.18 I'd suggest that your only sane
>> hope for us to help you track done the problem is to upgrade
>> to a current kernel and go from there....
> Thanks again Dave. But we can't upgrade the kernel as it is already in
> production and on field.
Yes, but you can run it in your test environment where you are
reproducing this problem, right?
> So do you think, periodic cleaning of file system using xfs_fsr can
> solve the issue?
No, at best it would only delay the problem (whatever it is).
> If not, could you
> kindly direct me what all patches were fixing similar problem? I can try
> back porting them.
I don't have time to try to identify some set of changes from the
past 3-4 years that might fix your problem. There may not even be a
patch that fixes your problem, which is one of the reasons why I've
asked if you can reproduce it on a current kernel....
I pointed you the files that the bug could lie in earlier in the
thread. You can find the history of changes to those files via the
mainline git repository or via the XFS CVS repository. You'd
probably do best to look at the git tree because all the changes are
well described in the commit logs and you should be able to isolate
ones that fix btree problems fairly easily...