From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275340AbTHMTyA (ORCPT ); Wed, 13 Aug 2003 15:54:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275332AbTHMTyA (ORCPT ); Wed, 13 Aug 2003 15:54:00 -0400 Received: from uns-y4.unisinos.br ([200.188.162.4]:25561 "EHLO sav03.unisinos.br") by vger.kernel.org with ESMTP id S275420AbTHMTxK (ORCPT ); Wed, 13 Aug 2003 15:53:10 -0400 From: Lucas Correia Villa Real To: Stephan von Krawczynski Subject: Re: 2.4.21 + NFS oops Date: Wed, 13 Aug 2003 16:42:29 -0300 User-Agent: KMail/1.5 Cc: linux-kernel@vger.kernel.org References: <200308121440.24983.lucasvr@gobolinux.org> <20030812233256.21c80830.skraw@ithnet.com> <200308131612.49627.lucasvr@gobolinux.org> In-Reply-To: <200308131612.49627.lucasvr@gobolinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200308131642.29018.lucasvr@gobolinux.org> X-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 13 August 2003 04:12 pm, Lucas Correia Villa Real wrote: > On Tuesday 12 August 2003 06:32 pm, Stephan von Krawczynski wrote: > > On Tue, 12 Aug 2003 14:40:24 -0300 > > > > Lucas Correia Villa Real wrote: > > > Hi, > > > > > > I have been trying to export an reiserfs partition on NFS. I can mount > > > it remotely and even create files on it, but I always got a kernel oops > > > when trying to remove any file. I have also tryied to export another > > > partition, formatted as ext2 (but keeping my root fs as reiserfs), but > > > the problem has persisted. > > > > Have you tried to compile your kernel with another compiler (i.e. not gcc > > 3.2.X) ? > > Well, I have just compiled it with GCC 2.95.3, and I got the same kernel > oops. By the way, I have formatted the whole disk with XFS, so it seems > like this isn't a reiserfs issue. > > Anyone suffering from NFS on 2.4.21, too, or any ideas...? Nevermind. It was a broken patch being applied without being noticed. Thanks, Lucas