From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Karl Hiramoto <karl@hiramoto.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-net@vger.kernel.org
Subject: Re: nfs root error after modprobe iptable_nat
Date: Thu, 10 Jul 2008 13:10:29 -0400 [thread overview]
Message-ID: <1215709829.7126.11.camel@localhost> (raw)
In-Reply-To: <48760ECF.1060103@hiramoto.org>
On Thu, 2008-07-10 at 15:29 +0200, Karl Hiramoto wrote:
> Hi all,
>
> loading nf_nat seems to cut my NFS root connection.
>
> # modprobe iptable_nat
> nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> # nfs: RPC call returned error 1
> nfs: RPC call returned error 1
>
>
>
> 12:23:35.335832 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 136) 192.168.10.54.4259114599 > 192.168.10.51.2049: 108
> lookup [|nfs]
> 12:23:35.335920 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 56) 192.168.10.51.2049 > 192.168.10.54.4259114599:
> reply ok 28 lookup ERROR: No such file or directory
> 12:23:35.336611 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 136) 192.168.10.54.4259114600 > 192.168.10.51.2049: 108
> lookup [|nfs]
> 12:23:35.336650 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
> UDP (17), length 56) 192.168.10.51.2049 > 192.168.10.54.4259114600:
> reply ok 28 lookup ERROR: No such file or directory
>
>
>
> NFS server:
> uname -a
> Linux karl-d820 2.6.25.10 #1 SMP Thu Jul 10 10:15:44 CEST 2008 i686
> Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux
>
>
>
> NFS Client:
> # uname -a
> Linux NSB 2.6.25.10 #6 Thu Jul 10 13:04:15 CEST 2008 armv5teb unknown
> uclibc 0.29
> Intel IXP425
>
>
> On the server there are no error messages. without loading NAT
> everything seems to work fine.
>
>
> Comping NAT directly into the kernel also has the same results.
>
>
> Not sure if i have something configured wrong, or if this is related to
> the patches sent by Trond a few days ago.
errno 1 is the same as EPERM (i.e. permission denied). I'm not sure what
is returning that error, but it isn't the NFS or SUNRPC layer.
Have you tried a 'git bisect'?
Cheers
Trond
prev parent reply other threads:[~2008-07-10 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 13:29 nfs root error after modprobe iptable_nat Karl Hiramoto
2008-07-10 17:10 ` Trond Myklebust [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=1215709829.7126.11.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=karl@hiramoto.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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.