xfs
[Top] [All Lists]

Re: XFS breakage in 2.6.18-rc1

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: XFS breakage in 2.6.18-rc1
From: Jeffrey Hundstad <jeffrey.hundstad@xxxxxxxx>
Date: Thu, 20 Jul 2006 00:51:22 -0500
Cc: Mattias Hedenskog <ml@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20060720090109.F1947140@wobbly.melbourne.sgi.com>
References: <67dc30140607190717r57ed2fe5w719dcca896110d8@mail.gmail.com> <44BE48D5.7020107@mnsu.edu> <20060720090109.F1947140@wobbly.melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (X11/20060713)
Nathan Scott wrote:
On Wed, Jul 19, 2006 at 09:59:33AM -0500, Jeffrey E. Hundstad wrote:
I did try the xfs_repair 2.8.4 for a volume running on 2.6.17.4 and it annihilated the volume. This volume was not showing signs of crashing. So... I guess I would certainly not run xfs_repair unless there is good reason.

Erm, wha..? Can you expand on "annihilated" a bit? (please send
me the full xfs_repair output if you still have it).

Nathan Scott,

I'm very sorry; I don't have the output anymore. By annihilated I mean that there were several directories trees that /didn't work/. If you tried to cd into the directory or take a directory listing... or used a file that you knew was in these certain directories then you'd get pages of debug message to the console; and no usable data. I re-ran xfs_repair and retried several times but the condition never seemed to improve or get worse for that matter.

I /incorrectly/ figured it was a known issue or I'd have saved the output. Sorry again.

--
Jeffrey Hundstad


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