All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au,
	nfs@lists.sourceforge.net
Subject: Re: [BUG] nfs version 2 broken
Date: Wed, 01 Feb 2006 20:19:22 +0100	[thread overview]
Message-ID: <43E109BA.2070004@t-online.de> (raw)
In-Reply-To: <1138812065.7858.6.camel@lade.trondhjem.org>

Trond Myklebust wrote:

>Does it do the same if you mount the same partition normally (i.e. not
>through nfsroot) in some other directory?
>
>  
>

That also fails. Same error message.

Unlike the nfsroot code at least my version of mount
does not use nfs version 2 as the default. I had to force
a v2 nfs mount attempt with mount -o nfsvers=2 ...

Would it be a good idea to change the default nfs version
nfsroot uses? I think nfsroot and mount defaults should
be identical.

BTW: Google shows some related old threads, e.g. "Madhan" writes on
2 Aug. 2001 06:55  "There has been a change in the NFS Client
behaviour in Linux Kernel  2.4.3 onwards.  There are 2 issues here,
1. as traces show new clients expect link count '1' and NetWare
NFS has  been sending '0' for volumes. ..."

cu,
 Knut

      reply	other threads:[~2006-02-01 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  6:07 [BUG] nfs version 2 broken Knut Petersen
2006-02-01  6:15 ` Trond Myklebust
2006-02-01  6:34   ` Knut Petersen
2006-02-01  6:35     ` Trond Myklebust
2006-02-01  6:46       ` Knut Petersen
2006-02-01  6:46         ` Knut Petersen
2006-02-01  7:13       ` Knut Petersen
2006-02-01  7:13         ` Knut Petersen
2006-02-01 16:41         ` Trond Myklebust
2006-02-01 19:19           ` Knut Petersen [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=43E109BA.2070004@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.