linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: frowand@mvista.com
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mount via nfs using MontaVista's Linux for IBM405
Date: Wed, 06 Dec 2000 11:02:46 +0100	[thread overview]
Message-ID: <3A2E0EC6.A1239E1A@esd-electronics.com> (raw)
In-Reply-To: 3A2D4B81.F0238326@mvista.com


Hello Frank,

I tried the nolock option for the mount command. It does not really
work, only sometimes, not very
frequently.

Here is exactly how I do the mount:

mount -t nfs -o nolock -v 192.168.2.190:/home/matthias/canbtgw
/home/matthias

(All directories exist, mounting from other computers is working.)

Here is the output:

  nfs warning: mount version older than kernel
  192.168.2.190:/home/matthias/canbtgw on /home/matthias type nfs
(rw,nolock,addr=192.168.2.190)
... long time later ...
  VFS: Close: file count is 0
  VFS: Close: file count is 0
... long time later ...
  VFS: Close: file count is 0

... mount never returns ...

Any further idea ?

Matthias

Frank Rowand wrote:
>
> Matthias Fuchs wrote:
> >
> > Hello,
> >
> > I am trying to mount a directory from a nfs server to my IBM405GP board.
> >
> > Here are the facts:
> >
> >         Kernel on our 405 board: 2.4.0-test2_mvista_001126
> >         Root filesystem: target_ftest4 from MontaVista
> >
> > When I do a: mount -t nfs <nfs-servers-ip>:/home/matthias /test on the
> > 405 board, I get this output (after some delay):
> >
> >         nfs warning: mount version older than kernel
> >         portmap: server localhost not responding, timed out
> >         portmap: server localhost not responding, timed out
> >         lockd_up: makesock failed, error=-5
> >
> > But I can still telnet to the board (it does not crash) but I cannot
> > interrupt the mount call.
> >
> > The nfs server is working properly, because I get the root filesystem
> > from the same server (with no problems).
> >
> > Has anybody a solution for this problem ?
> >
> > Matthias
> > --
>
> Add the "-o nolock" option to the mount command.
>
> -Frank
> --
> Frank Rowand <frank_rowand@mvista.com>
> MontaVista Software, Inc

--
-------------------------------------------------
\ Matthias Fuchs                                 \
 \ esd electronic system design Gmbh              \
  \ Vahrenwalder Straße 205                        \
   \ D-30165 Hannover                               \
    \ email: matthias.fuchs@esd-electronics.com      \
     \ phone: +49-511-37298-0                         \
      \ fax:   +49-511-37298-68                        \
       --------------------------------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-12-06 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05 10:21 mount via nfs using MontaVista's Linux for IBM405 Matthias Fuchs
2000-12-05 11:59 ` Topi Kanerva
2000-12-05 12:20   ` Wolfgang Denk
2000-12-05 20:09 ` Frank Rowand
2000-12-06 10:02   ` Matthias Fuchs [this message]
2000-12-06 18:53     ` Frank Rowand

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=3A2E0EC6.A1239E1A@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.com \
    --cc=frowand@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).