From: Santiago <santi@mleads.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: RedHat/Mandrake NFS - not playing nice
Date: Mon, 17 Feb 2003 15:04:30 -0700 [thread overview]
Message-ID: <3E515C6E.6040609@mleads.com> (raw)
In-Reply-To: shswujywwe6.fsf@charged.uio.no
Thanks for responding so quickly Trond. I'm replying inline.
Trond Myklebust wrote:
>>>>>>" " == santi <Santiago> writes:
>>>>>
>
> > The Mandrake 9.0 is stock distro with kernel 2.4.19-ac4
> > (custom) with NFS support compiled in.
>
> You appear to have forgotten to compile NFSv3 into this kernel. Try to
> specify the option '-onfsvers=2'.
I recompiled the kernel to support all versions of NFS:
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x
x x < > Coda file system support (advanced network fs)
x x < > InterMezzo file system
support (experimental,
x x <*> NFS file system support
x x [*] Provide NFSv3 client
support x x
<*> NFS server support
x x [*] Provide NFSv3 server support
x x [*] Provide NFS
server over TCP support (EXPERIMENTAL) x x
<*> SMB file system support (to mount Windows shares
x x [*] Use a default NLS
x x
Default Remote NLS Option: "cp437"
x x < > NCP file system support (to mount NetWare
volumes) x x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
x
tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu
x <Select> < Exit > < Help >
x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
> You appear also not to be running rpc.statd on that machine. Unless
> you also use the 'nolock' mount option, you will end up with problems
> the first time some process tries to lock a file.
I took care of this too. Thanks for pointing it out.
[root@backup linux]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 682 rquotad
100011 2 udp 682 rquotad
100011 1 tcp 685 rquotad
100011 2 tcp 685 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100021 1 tcp 32796 nlockmgr
100021 3 tcp 32796 nlockmgr
100021 4 tcp 32796 nlockmgr
100005 1 udp 32771 mountd
100005 1 tcp 32797 mountd
100005 2 udp 32771 mountd
100005 2 tcp 32797 mountd
100005 3 udp 32771 mountd
100005 3 tcp 32797 mountd
100024 1 udp 32772 status
100024 1 tcp 32798 status
However, I still am receiving the same error as before:
[root@backup linux]# mount 10.0.0.48:/var/www/html /r/amanda/nitro-html
-t nfs
mount: 10.0.0.48:/var/www/html failed, reason given by server:
Permission denied
[root@backup linux]#
Any more ideas or suggestions?
Thanks,
Santiago
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-17 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:41 RedHat/Mandrake NFS - not playing nice Santiago
2003-02-17 19:16 ` Trond Myklebust
2003-02-17 22:04 ` Santiago [this message]
2003-02-17 22:28 ` Paul Heinlein
2003-02-18 14:30 ` Santiago
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=3E515C6E.6040609@mleads.com \
--to=santi@mleads.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox