From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030394AbWGTWxR (ORCPT ); Thu, 20 Jul 2006 18:53:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030395AbWGTWxR (ORCPT ); Thu, 20 Jul 2006 18:53:17 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:46799 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S1030394AbWGTWxQ (ORCPT ); Thu, 20 Jul 2006 18:53:16 -0400 Date: Fri, 21 Jul 2006 08:52:30 +1000 From: Nathan Scott To: Justin Piszcz Cc: Chris Wedgwood , David Greaves , Kasper Sandberg , Torsten Landschoff , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, ml@magog.se, radsaq@gmail.com Subject: Re: FAQ updated (was Re: XFS breakage...) Message-ID: <20060721085230.F1990742@wobbly.melbourne.sgi.com> References: <20060718222941.GA3801@stargate.galaxy> <20060719085731.C1935136@wobbly.melbourne.sgi.com> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@wobbly.melbourne.sgi.com> <44BF8500.1010708@dgreaves.com> <20060720161121.GA26748@tuatara.stupidest.org> <20060721081452.B1990742@wobbly.melbourne.sgi.com> <20060721082448.C1990742@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jpiszcz@lucidpixels.com on Thu, Jul 20, 2006 at 06:43:34PM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 20, 2006 at 06:43:34PM -0400, Justin Piszcz wrote: > p34:~# xfs_check -v /dev/md3 > xfs_check: out of memory > p34:~# > > D'oh... xfs_repair -n is another option, it has a cheaper (memory wise, usually) checking algorithm. > As long as it mounted ok with the patched kernel, should one be ok? Not necessarily, no - mount will only read the root inode. cheers. -- Nathan