Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5LKvKnC014230 for ; Fri, 21 Jun 2002 13:57:20 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g5LKvK0w014229 for linux-xfs-outgoing; Fri, 21 Jun 2002 13:57:20 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-xfs@oss.sgi.com using -f Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g5LKvBnC014201 for ; Fri, 21 Jun 2002 13:57:12 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-7.quicknet.nl [212.58.163.7]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id g5LKxie0080431; Fri, 21 Jun 2002 22:59:44 +0200 (CEST) Message-Id: <4.3.2.7.2.20020621225412.03914c68@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 21 Jun 2002 22:59:47 +0200 To: Dave Alden , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Kernel oops with XFS and NFS In-Reply-To: <20020621144927.A1528@math.ohio-state.edu> References: <20020620200647.A8102@math.ohio-state.edu> <20020620200647.A8102@math.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 At 14:49 21-6-2002 -0400, Dave Alden wrote: >Hi, > Sorry to follup to my own message, but I'm getting extremely desperate. >I'm now at the point that I can't bring the system up for more than a few >minutes before it does the oops. I'm afraid I'm going to be forced to go >back to EXT3, and once I go back I probably won't get the opportunity to >try XFS again (please don't take this as a threat, it's just a plea for >help -- I really, really, really want to stay with XFS, but with 500 users >breaking down my door I don't know if it will be an option). Does anyone >have any suggestions? If the system oopses really fast after rebooting you may have some file system corruption. very slight corruption. You probably won't even have lost something but one of the structures might have gotten off for some reason which is causing this. When you do have the opportunity pleased update to a newer kernel. The 1.1 release from the 7.3 kernel has come a _really_ long way since 2.4.5 (IRC) If you can upgrade please do so. I had good luck with NFS and a XFS kernel (as in decent speed) starting with 2.4.6-pre5 which had numerous important fixes in the NFS path. There have been a lot more since that one as well. You are just unlucky at the moment that you have not hit that one yet. Try a clean reboot and then a xfs_repair. This has solved some issues in the past. Sorry for the slow response, I have a headache which makes pondering hurt. Cheers -- Seth It might just be your lucky day, if you only knew.