xfs
[Top] [All Lists]

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

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: FAQ updated (was Re: XFS breakage...)
From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Thu, 20 Jul 2006 18:43:34 -0400 (EDT)
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: <20060721082448.C1990742@xxxxxxxxxxxxxxxxxxxxxxxx>
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> <20060721082448.C1990742@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx


On Fri, 21 Jul 2006, Nathan Scott wrote:

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.

cheers.

--
Nathan



p34:~# xfs_check -v /dev/md3
xfs_check: out of memory
p34:~#

D'oh...

1GB ram, 2GB swap trying to check a 2.6T fs, no dice.

As long as it mounted ok with the patched kernel, should one be ok?


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