[Top] [All Lists]

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

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: FAQ updated (was Re: XFS breakage...)
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 21 Jul 2006 08:24:49 +1000
Cc: Chris Wedgwood <cw@xxxxxxxx>, David Greaves <david@xxxxxxxxxxxx>, Kasper Sandberg <lkml@xxxxxxxxxxx>, Torsten Landschoff <torsten@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, ml@xxxxxxxx, radsaq@xxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0607201817450.23697@xxxxxxxxxxxxxxxx>; from jpiszcz@xxxxxxxxxxxxxxx on Thu, Jul 20, 2006 at 06:18:14PM -0400
References: <20060718222941.GA3801@xxxxxxxxxxxxxxx> <20060719085731.C1935136@xxxxxxxxxxxxxxxxxxxxxxxx> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@xxxxxxxxxxxxxxxxxxxxxxxx> <44BF8500.1010708@xxxxxxxxxxxx> <20060720161121.GA26748@xxxxxxxxxxxxxxxxxxxxx> <20060721081452.B1990742@xxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0607201817450.23697@xxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Thu, Jul 20, 2006 at 06:18:14PM -0400, Justin Piszcz wrote:
> Nathan,
> Does the bug only occur during a crash?

No, its unrelated to crashing.  Only when adding/removing from a
directory that is in a specific node/btree format (many entries),
and only under a specific set of conditions (like what directory
entry names were used, which blocks they've hashed to and how they
ended up being allocated and in what order each block gets removed
from the directory).

> I have been running 2.6.17.x for awhile now (multiple XFS filesystems, all 
> on UPS) - no issue?

Could be an issue, could be none.  xfs_check it to be sure.



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