Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id g6K7xPRw003636 for ; Sat, 20 Jul 2002 00:59:25 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id g6K7xPmG003634 for linux-xfs-outgoing; Sat, 20 Jul 2002 00:59:25 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-xfs@oss.sgi.com using -f Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id g6K7xJRw003594 for ; Sat, 20 Jul 2002 00:59:20 -0700 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id B69E11448F; Sat, 20 Jul 2002 09:59:56 +0200 (MEST) Date: Sat, 20 Jul 2002 09:59:56 +0200 From: Andi Kleen To: Poul Petersen Cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.18 XFS 1.1 : Gave up on XFS - too many Oops Message-ID: <20020720095956.A3994@wotan.suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Have you tried the usual tests like running memtest86 overnight to make sure you don't have a bad DIMM or some other hardware problem? When you switch to another filesystem and still get crashes you will eventually know. If that is the case you could at least report to the list later that it wasn't XFS to blame. Also you should make sure you are using a good compiler to compile XFS (e.g. some versions of the RedHat 2.96 gcc were pretty bad) -Andi