From: Milos Jakovljevic <milos_sd-wj0mSnlwsj31P9xLtpHBDw@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: nfs server and client doesn't work in 2.6.32-rcX kernels
Date: Mon, 05 Oct 2009 14:54:18 +0200 [thread overview]
Message-ID: <1254747258.7129.7.camel@c2d-desktop> (raw)
Hi.
I compiled 2.6.32-rc3 (and rc1(2) before that) on one PC. On the other
PC I have 2.6.31 kernel.
NFS-Server problem:
When I try to restart nfs-kernel-server service it says that my kernel
doesn't have nfs-server support. That is when nfs-server support is
compiled as a module, but when I compile it as part of a kernel it
works.
NFS client problem:
I tried to compile it as part of the kernel and as module, but I alweys
have the same situation:
I try to mount nfs share that is on other PC (that has 2.6.31 kernel),
and it seems it mounts ok. But when I go to that directory and do: "ls",
I get errors saying: "input/output error" for every directory that nfs
share has in it.
I don't know if the problem is in compitability with older kernels or
with "nfs-kernel-server and nfs-common" packages in Ubuntu 9.04.
reply other threads:[~2009-10-05 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1254747258.7129.7.camel@c2d-desktop \
--to=milos_sd-wj0msnlwsj31p9xltphbdw@public.gmane.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox