From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 25 Aug 2008 20:36:27 -0700 (PDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id m7Q3aOdw025513 for ; Mon, 25 Aug 2008 20:36:24 -0700 Received: from mail.flatline.de (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 79D13FBC210 for ; Mon, 25 Aug 2008 20:37:46 -0700 (PDT) Received: from mail.flatline.de (flatline.de [80.190.243.144]) by cuda.sgi.com with ESMTP id sPMKqgwSFFtqbqIi for ; Mon, 25 Aug 2008 20:37:46 -0700 (PDT) Date: Tue, 26 Aug 2008 05:37:41 +0200 From: Andreas Kotes Subject: Re: XFS internal error Message-ID: <20080826033741.GX21319@slop.flatline.de> References: <20080310122216.GG14256@slop.flatline.de> <20080310223018.GA155407@sgi.com> <20080310225927.GP14256@slop.flatline.de> <20080310234539.GC155407@sgi.com> <20080311134746.GQ14256@slop.flatline.de> <20080312175050.GD14256@slop.flatline.de> <20080313000121.GU155407@sgi.com> <20080313071445.GA30874@slop.flatline.de> <20080313071744.GB30874@slop.flatline.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Allan Haywood Cc: David Chinner , "xfs@oss.sgi.com" Hello, I think that might have been an issue on our FS as well. No, no resolution, no debugging advice, etc .. We've basically had to ignore it - and it didn't surface a lot more, now you mention it. We are working far less close to 100% than before, though ... *thinking* Andreas * Allan Haywood [20080825 20:58]: > Sorry for top posting on this reply, but I was wondering if there was any resolution to your problem below. We seem to be running into a similar problem. A few hours before the error in this thread occurred the filesystem was filled up to 100%, we had to clean things up to continue running. > > Any additional information would be great. > > -----Original Message----- > From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com] On Behalf Of Andreas Kotes > Sent: Thursday, March 13, 2008 12:18 AM > To: David Chinner > Cc: xfs@oss.sgi.com > Subject: Re: XFS internal error > > * Andreas Kotes [20080313 08:14]: > > * David Chinner [20080313 01:01]: > > > On Wed, Mar 12, 2008 at 06:50:50PM +0100, Andreas Kotes wrote: > > > > * Andreas Kotes [20080311 14:47]: > > > > > I basically build a PXE image which does an xfs_repair -L /dev/sda2 from > > > > > initrd - and the problem persists. Sigh. Exactly no change. > > > > > > Do you do this on every boot? > > > > no, I did this on a6b and a7b so far, where the problems I mentioned > > occur, and only after I saw these in-memory problems. in general, XFS > > proves to be realiable for us. > > > > would you recommend running an xfs_check before running an xfs_repair in > > case of problems? > > oh, btw - running xfs_check doesn't work most of the time, as the log > usually contains entries, and isn't replayed before shutdown .. > > I figure running this on every boot would leave me killing my log all of > the time, if the shutdown didn't leave time to write the changes to > disk? ;)