From: Oleg Drokin <green@namesys.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: David Ford <david+powerix@blue-labs.org>,
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: Mon, 3 Feb 2003 14:12:36 +0300 [thread overview]
Message-ID: <20030203141236.A18736@namesys.com> (raw)
In-Reply-To: <15931.62606.441404.74917@charged.uio.no>
Hello!
On Sat, Feb 01, 2003 at 05:23:42PM +0100, Trond Myklebust wrote:
> > 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?
While trying to reproduce mounting of reiserfs FS over NFS from 2.5.59 server,
trying to see if there is something to do with reiserfs itself (and it worked
perfectly with 2.4.19 client), I decided to try to mount it from this same
workstation as I did not had 2.5.59 client at hand.
This way I learned that mount localhost:/exportedfs /mnt -t nfs
(localhost can be replaced by any local IP) results in mount
hanging in D state:
100 0 775 770 15 0 1532 620 rpc_ex D pts/1 0:00 mount 212.16.7.78:/home /mnt -t nfs
At the same time I still can mount it from external hosts (but cannot kill this hung mount, obviously).
This is on today's 2.5.529 bk snapshot.
Bye,
Oleg
prev parent reply other threads:[~2003-02-03 11:03 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
2003-02-03 11:12 ` Oleg Drokin [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=20030203141236.A18736@namesys.com \
--to=green@namesys.com \
--cc=akpm@digeo.com \
--cc=david+powerix@blue-labs.org \
--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