xfs
[Top] [All Lists]

Re: xfs recovery oops in 2.6.4-mm1

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: xfs recovery oops in 2.6.4-mm1
From: William Lee Irwin III <wli@xxxxxxxxxxxxxx>
Date: Sun, 14 Mar 2004 15:36:04 -0800
Cc: Steve Lord <lord@xxxxxxx>, tes@xxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <20040314233054.GA643@frodo>
Organization: The Domain of Holomorphy
References: <20040312100025.GP655@holomorphy.com> <4051D517.4070005@xfs.org> <20040312233153.GT655@holomorphy.com> <4052834B.5010208@xfs.org> <20040314233054.GA643@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.5.1+cvs20040105i
On Fri, Mar 12, 2004 at 09:19:51AM -0600, Steve Lord wrote:
>> Have you successfully used xfs on this box with older kernels, or is
>> this a new filesystem? Was this the first mount under 2.6.4-mm1?

On Mon, Mar 15, 2004 at 10:30:54AM +1100, Nathan Scott wrote:
> This would be useful to know.

I created it first with 2.6.3-mm4.


On Mon, Mar 15, 2004 at 10:30:54AM +1100, Nathan Scott wrote:
> Attached is a test program thats been used to exercise log
> recovery in a more user-friendly fashion.  It uses the xfs
> forced-shutdown mode to get a dirty log without having to
> pull the plug.  So, generate traffic, shutdown, unmount, &
> then the next mount will do log recovery.  If you find the
> right traffic to generate a reproducible failure, diagnosing
> this becomes a whole lot easier.  There's other tools for
> generating all manner of different types of traffic in the
> xfstests directory in the xfs userspace cvs too - fsstress
> is a good one for generating lots of metadata operations.

Well, it sort of crapped itself in the midst of doing large
recovery ops, so I think marking it dirty and replaying nothing
won't fly, but pulling the plug in the midst of fsstress sounds
like a good bet.


-- wli


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