xfs
[Top] [All Lists]

Re: Linux 2.4.22 XFS 1.3.1 reservation ran out

To: Eric Sandeen <sandeen@xxxxxxx>
Subject: Re: Linux 2.4.22 XFS 1.3.1 reservation ran out
From: Soumen Chakrabarti <soumen@xxxxxxxxxxxxxx>
Date: Fri, 28 Nov 2003 11:35:56 +0530
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.44.0310270844480.9654-100000@xxxxxxxxxxxxxxxxxxxxxx>
References: <Pine.LNX.4.44.0310270844480.9654-100000@xxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
Eric Sandeen wrote:
On Sun, 26 Oct 2003, Soumen Chakrabarti wrote:
Repeatable bug, here's how to create the situation:
1. Start with a fresh install of stock RedHat 9.
2. Download kernel 2.4.22.
3. Patch in XFS 1.3.1 and build new kernel.

Ok, for starters, i don't think we shipped patches specifically
for xfs 1.3.1 + kernel 2.4.22, and the patches we did ship for 2.4.21
do not apply cleanly to 2.4.22.

I downloaded the patch around 10/15, from this URL:
ftp://oss.sgi.com/projects/xfs/patches/2.4.22
which seems to indicate that even on that date, there was a patch available for 2.4.22 (maybe I looked where I should not). Today (11/28), I can't even find a patch for 2.4.21 (at least not by moving up to the parent dir ...patches/).

Some other people seem to have confirmed in the meantime that the problem shown by bonnie on 2.4.22 + 1.3.1 is a real one.

I have some time now to either roll back to 2.4.21 if that is known to fix the problem, OR to rebuild a 2.4.22 kenel, given that the "all" patch file has changed in size and is now timestamped 11/10. I'd appreciate it very much if a XFS developer can confirm what has happened to this bug and if the 11/10 patch fixes it. Thanks.



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