[Top] [All Lists]

Re: FAQ updated (was Re: XFS breakage...)

To: David Greaves <david@xxxxxxxxxxxx>
Subject: Re: FAQ updated (was Re: XFS breakage...)
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Thu, 20 Jul 2006 09:11:21 -0700
Cc: Nathan Scott <nathans@xxxxxxx>, Kasper Sandberg <lkml@xxxxxxxxxxx>, Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, Torsten Landschoff <torsten@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, ml@xxxxxxxx, radsaq@xxxxxxxxx
In-reply-to: <44BF8500.1010708@xxxxxxxxxxxx>
References: <20060718222941.GA3801@xxxxxxxxxxxxxxx> <20060719085731.C1935136@xxxxxxxxxxxxxxxxxxxxxxxx> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@xxxxxxxxxxxxxxxxxxxxxxxx> <44BF8500.1010708@xxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
On Thu, Jul 20, 2006 at 02:28:32PM +0100, David Greaves wrote:

> Does this problem exist in 2.16.6.x??

The change was merged after 2.6.16.x was branched, I was mistaken
in how long I thought the bug has been about.

> I hope so because I assumed there simply wasn't a patch for 2.6.16 and
> applied this 'best guess' to my servers and rebooted/remounted successfully.

Doing the correct change to 2.6.16.x won't hurt, but it's not

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