From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932561AbWGSXBs (ORCPT ); Wed, 19 Jul 2006 19:01:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932562AbWGSXBs (ORCPT ); Wed, 19 Jul 2006 19:01:48 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:37829 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S932561AbWGSXBr (ORCPT ); Wed, 19 Jul 2006 19:01:47 -0400 Date: Thu, 20 Jul 2006 09:01:09 +1000 From: Nathan Scott To: "Jeffrey E. Hundstad" Cc: Mattias Hedenskog , linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: XFS breakage in 2.6.18-rc1 Message-ID: <20060720090109.F1947140@wobbly.melbourne.sgi.com> References: <67dc30140607190717r57ed2fe5w719dcca896110d8@mail.gmail.com> <44BE48D5.7020107@mnsu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <44BE48D5.7020107@mnsu.edu>; from jeffrey.hundstad@mnsu.edu on Wed, Jul 19, 2006 at 09:59:33AM -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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). thanks. -- Nathan