linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Correia Villa Real <lucasvr@gobolinux.org>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 + NFS oops
Date: Wed, 13 Aug 2003 16:42:29 -0300	[thread overview]
Message-ID: <200308131642.29018.lucasvr@gobolinux.org> (raw)
In-Reply-To: <200308131612.49627.lucasvr@gobolinux.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 <lucasvr@gobolinux.org> 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


      reply	other threads:[~2003-08-13 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 17:40 2.4.21 + Reiserfs + NFS oops Lucas Correia Villa Real
2003-08-12 21:32 ` Stephan von Krawczynski
2003-08-12 23:13   ` Lucas Correia Villa Real
2003-08-13 19:12   ` 2.4.21 " Lucas Correia Villa Real
2003-08-13 19:42     ` Lucas Correia Villa Real [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200308131642.29018.lucasvr@gobolinux.org \
    --to=lucasvr@gobolinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).