Received: with ECARTIS (v1.0.0; list xfs); Mon, 25 Aug 2008 11:56:50 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.0-r574664 (2007-09-11) on oss.sgi.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.0-r574664 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 m7PIulV3010797 for ; Mon, 25 Aug 2008 11:56:47 -0700 X-ASG-Debug-ID: 1219690689-100803510000-NocioJ X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from mx1.myoutlookonlinE.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 613A7FB4CEA for ; Mon, 25 Aug 2008 11:58:09 -0700 (PDT) Received: from mx1.myoutlookonlinE.com (mx1.myoutlookonline.com [69.25.74.52]) by cuda.sgi.com with ESMTP id mGYtVUL38pgCVOWT for ; Mon, 25 Aug 2008 11:58:09 -0700 (PDT) Received: from BE130.mail.lan ([10.109.208.130]) by mx1.myoutlookonlinE.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 25 Aug 2008 14:58:09 -0400 Received: from HUB012.mail.lan ([10.109.208.62]) by BE130.mail.lan with Microsoft SMTPSVC(6.0.3790.3959); Mon, 25 Aug 2008 14:58:08 -0400 Received: from BE181.mail.lan ([10.109.208.181]) by HUB012.mail.lan ([10.109.208.62]) with mapi; Mon, 25 Aug 2008 14:58:08 -0400 From: Allan Haywood To: Andreas Kotes , David Chinner CC: "xfs@oss.sgi.com" Date: Mon, 25 Aug 2008 14:58:06 -0400 X-ASG-Orig-Subj: RE: XFS internal error Subject: RE: XFS internal error Thread-Topic: XFS internal error Thread-Index: AciE2pRU3vLlKD7TQGa7C+Lncszr5iCCajkQ Message-ID: References: <470831E6.4030704@fastmail.co.uk> <20071008001452.GX995458@sgi.com> <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> In-Reply-To: <20080313071744.GB30874@slop.flatline.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginalArrivalTime: 25 Aug 2008 18:58:08.0853 (UTC) FILETIME=[83B18850:01C906E4] X-Barracuda-Connect: mx1.myoutlookonline.com[69.25.74.52] X-Barracuda-Start-Time: 1219690690 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Virus-Scanned: by cuda.sgi.com at sgi.com X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using per-user scores of TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.3699 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-Virus-Scanned: ClamAV 0.91.2/8086/Mon Aug 25 05:20:55 2008 on oss.sgi.com X-Virus-Status: Clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id m7PIulV3010799 X-archive-position: 17711 X-ecartis-version: Ecartis v1.0.0 Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com X-original-sender: ahaywood@datallegro.com Precedence: bulk X-list: xfs 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. Thanks. -Allan Haywood -----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 Hello, * 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? ;) Andreas -- flatline IT services - Andreas Kotes - Tailored solutions for your IT needs