All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Julius <julius.junghans@gmx.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: root over nfs, error -93
Date: Wed, 28 May 2008 18:23:40 -0400	[thread overview]
Message-ID: <483DDB6C.4040209@oracle.com> (raw)
In-Reply-To: <1212009456.3786.24.camel@wf>

[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]

Julius wrote:
> Hi,
> 
> 
> im trying to get a client boot from my server via nfs. but it fails
> with:
> 
> Root-NFS: Server returned error -93 while
> mounting /nfs-exports/pxeclient

Error 93 is EPROTONOSUPPORT.  Is there a firewall between client and 
server?  tcpwrappers on either end?  Are you using a motherboard NIC 
that silently hijacks a reserved UDP port?

Try capturing a network trace with "tcpdump -s0 -w /tmp/dump" on your 
server while your client boots.  Take a look at it with wireshark or 
tethereal.

> the client uses a vanilla 2.6.24.7 kernel with these settings:
> <*>   NFS file system support 
>  [*]     Provide NFSv3 client support 
>  [*]       Provide client support for the NFSv3 ACL protocol extension 
>  [*]   Root file system on NFS
>  [*]   Support for rpcbind versions 3 & 4 (EXPERIMENTAL)
> 
> 
> full config:
> http://metalfan2.me.funpic.de/.config
> 
> 
> kernel append line:
> append root=/dev/nfs nfsroot=192.168.11.3:/nfs-exports/pxeclient ip=dhcp
> 
> 
> the system successfully boots the kernel via syslinux and requests its
> ip via dhcp
> 
> 
> server:
> rpcinfo -p localhost
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100024    1   udp  54039  status
>     100024    1   tcp  57693  status
>     100005    3   udp  48497  mountd
>     100005    3   tcp  34406  mountd
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100003    4   udp   2049  nfs
>     100021    1   udp  47061  nlockmgr
>     100021    3   udp  47061  nlockmgr
>     100021    4   udp  47061  nlockmgr
>     100003    2   tcp   2049  nfs
>     100003    3   tcp   2049  nfs
>     100003    4   tcp   2049  nfs
>     100021    1   tcp  54896  nlockmgr
>     100021    3   tcp  54896  nlockmgr
>     100021    4   tcp  54896  nlockmgr
> 
> nfs-utils-1.1.0
> 
> 
> 
> Any ideas whats wrong?
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: chuck_lever.vcf --]
[-- Type: text/x-vcard, Size: 259 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


  parent reply	other threads:[~2008-05-28 22:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 21:17 root over nfs, error -93 Julius
2008-05-28 21:31 ` david m. richter
2008-05-28 22:24   ` Julius
2008-05-28 22:23 ` Chuck Lever [this message]
2008-05-29  0:04 ` Trond Myklebust
2008-05-29 10:01   ` Julius
2008-06-01  8:22   ` Julius

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=483DDB6C.4040209@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=julius.junghans@gmx.de \
    --cc=linux-nfs@vger.kernel.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 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.