From: David Ford <david+cert@blue-labs.org>
To: trond.myklebust@fys.uio.no
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Neil Brown <neilb@cse.unsw.edu.au>,
Andrew Morton <akpm@digeo.com>
Subject: Re: NFS problems, 2.5.5x
Date: Sat, 01 Feb 2003 16:49:29 -0500 [thread overview]
Message-ID: <3E3C40E9.1010901@blue-labs.org> (raw)
In-Reply-To: <15931.62606.441404.74917@charged.uio.no>
Yes. Today I haven't experienced the loop problem. On the other hand,
when I reboot back and forth between 2.5.53 and 2.5.59, I have to
restart the server nfs programs or I get permission denied on the client
and "rpc.mountd: getfh failed: Operation not permitted" on the server.
I have also had to restart 2.4 clients because NFS silently hangs. I
believe there's a few patches on the list that I need to apply regarding
this.
David
Trond Myklebust wrote:
>>>>>>" " == David Ford <david+powerix@blue-labs.org> writes:
>>>>>>
>>>>>>
>
> > The last time NFS was working, I had 2.4.19 and 2.5.53 clients
> > on a
> > 2.5.59 server, that was yesterday. I had experienced a slight
> > problem
> > with it last week when my 2.5.53 client was booted for first
> > time on 2.5.5x, it was previously a 2.4 kernel. The server
> > OOPSed repeatedly shortly after bootup in NFS stuff then it
> > never happened again and was rock solid until today.
>
>So have you tried out the 2.5.53 client since you noticed this
>problem?
>
>Cheers,
> Trond
>
>
--
I may have the information you need and I may choose only HTML. It's up
to you. Disclaimer: I am not responsible for any email that you send me
nor am I bound to any obligation to deal with any received email in any
given fashion. If you send me spam or a virus, I may in whole or part
send you 50,000 return copies of it. I may also publically announce any
and all emails and post them to message boards, news sites, and even
parody sites. I may also mark them up, cut and paste, print, and staple
them to telephone poles for the enjoyment of people without internet
access. This is not a confidential medium and your assumption that your
email can or will be handled confidentially is akin to baring your
backside, burying your head in the ground, and thinking nobody can see
you butt nekkid and in plain view for miles away. Don't be a cluebert,
buy one from K-mart today.
When it absolutely, positively, has to be destroyed overnight.
AIR FORCE
next prev parent reply other threads:[~2003-02-01 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 2:13 NFS problems, 2.5.5x David Ford
2003-02-01 2:30 ` Andrew Morton
2003-02-01 2:46 ` David Ford
2003-02-01 8:58 ` Trond Myklebust
2003-02-01 16:03 ` David Ford
2003-02-01 16:23 ` Trond Myklebust
2003-02-01 21:49 ` David Ford [this message]
2003-02-03 11:12 ` Oleg Drokin
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=3E3C40E9.1010901@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=trond.myklebust@fys.uio.no \
/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