Skip to contentSkip to conversation

permission denied with nfs built into kernel 2.6.13

DISCUSSION Scott Leerssen 2 participants 3 messages Sep 13, 2005

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Thanks in advance for plowing through this message...

I have NFS built into a 2.6.13 kernel running on Fedora Core 3, and am unable to mount a filesystem on the server running the kernel. Output in /var/log/messages seems to indicate a successful mount request:

Sep 13 10:10:41 boot10-5-3-54 rpc.mountd: authenticated mount request from 10.5.1.1:870 for /I (/I)

However the client gives me this:

mount: 10.5.3.54:/I failed, reason given by server: Permission denied

Even though from the client:

[root@devmws5 fc3mws]# showmount -e 10.5.3.54
Export list for 10.5.3.54:
/I *

I've noticed that Fedora blindly assumes that all of the nfs related kernel code will load as modules, as there are a number of module install options that won't occur (like '/bin/mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs'). I probably just missed some obscure configuration option.

Here's a list of what I have....

nfs-utils-1.0.6-52

kernel config for NFS in case it helps:

linux 2.6.13 built with NFS in the kernel as follows:
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

/etc/exports:

/R *(rw,async,hide,insecure,no_root_squash,secure_locks) /I *(rw,async,hide,insecure,no_root_squash,secure_locks)

And, finally, output from the client:

[root@devmws5 fc3mws]# rpcinfo -p 10.5.3.54
program vers proto port

    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32769  status
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32774  nlockmgr
    100021    3   tcp  32774  nlockmgr
    100021    4   tcp  32774  nlockmgr
    100011    1   udp    871  rquotad
    100011    2   udp    871  rquotad
    100011    1   tcp    874  rquotad
    100011    2   tcp    874  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp    886  mountd
    100005    1   tcp    889  mountd
    100005    2   udp    886  mountd
    100005    2   tcp    889  mountd
    100005    3   udp    886  mountd
    100005    3   tcp    889  mountd

and from the server:

[root@boot10-5-3-54 ~]# rpcinfo -p localhost
program vers proto port

    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32769  status
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32774  nlockmgr
    100021    3   tcp  32774  nlockmgr
    100021    4   tcp  32774  nlockmgr
    100011    1   udp    871  rquotad
    100011    2   udp    871  rquotad
    100011    1   tcp    874  rquotad
    100011    2   tcp    874  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp    886  mountd
    100005    1   tcp    889  mountd
    100005    2   udp    886  mountd
    100005    2   tcp    889  mountd
    100005    3   udp    886  mountd
    100005    3   tcp    889  mountd

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#1 lore raw

Le mardi 13 Septembre 2005 16:23, Scott Leerssen a =E9crit=A0:

Quoted 11 lines

Thanks in advance for plowing through this message...

I have NFS built into a 2.6.13 kernel running on Fedora Core 3, and am unable to mount a filesystem on the server running the kernel. Output in /var/log/messages seems to indicate a successful mount request:

Sep 13 10:10:41 boot10-5-3-54 rpc.mountd: authenticated mount request

from 10.5.1.1:870 for /I (/I)

However the client gives me this:

Quoted 7 lines

mount: 10.5.3.54:/I failed, reason given by server: Permission denied

Even though from the client:

[root@devmws5 fc3mws]# showmount -e 10.5.3.54
Export list for 10.5.3.54:
/I *

I don't understand what you are exporting.
could you tell me the result of=20
exportfs -v
It should looks like=20
/export_nfs <world>(rw,wdelay,root_squash)

(nfs3)

Vincent

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

#2 lore raw
In reply to Scott Leerssen

Found the answer...

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126263

Quoted 103 lines · Scott Leerssen

Thanks in advance for plowing through this message...

I have NFS built into a 2.6.13 kernel running on Fedora Core 3, and am unable to mount a filesystem on the server running the kernel. Output in /var/log/messages seems to indicate a successful mount request:

Sep 13 10:10:41 boot10-5-3-54 rpc.mountd: authenticated mount request from 10.5.1.1:870 for /I (/I)

However the client gives me this:

mount: 10.5.3.54:/I failed, reason given by server: Permission denied

Even though from the client:

[root@devmws5 fc3mws]# showmount -e 10.5.3.54
Export list for 10.5.3.54:
/I *

I've noticed that Fedora blindly assumes that all of the nfs related kernel code will load as modules, as there are a number of module install options that won't occur (like '/bin/mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs'). I probably just missed some obscure configuration option.

Here's a list of what I have....

nfs-utils-1.0.6-52

kernel config for NFS in case it helps:

linux 2.6.13 built with NFS in the kernel as follows:
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y

/etc/exports:

/R *(rw,async,hide,insecure,no_root_squash,secure_locks) /I *(rw,async,hide,insecure,no_root_squash,secure_locks)

And, finally, output from the client:

[root@devmws5 fc3mws]# rpcinfo -p 10.5.3.54
program vers proto port

    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32769  status
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32774  nlockmgr
    100021    3   tcp  32774  nlockmgr
    100021    4   tcp  32774  nlockmgr
    100011    1   udp    871  rquotad
    100011    2   udp    871  rquotad
    100011    1   tcp    874  rquotad
    100011    2   tcp    874  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp    886  mountd
    100005    1   tcp    889  mountd
    100005    2   udp    886  mountd
    100005    2   tcp    889  mountd
    100005    3   udp    886  mountd
    100005    3   tcp    889  mountd

and from the server:

[root@boot10-5-3-54 ~]# rpcinfo -p localhost
program vers proto port

    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32769  status
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32774  nlockmgr
    100021    3   tcp  32774  nlockmgr
    100021    4   tcp  32774  nlockmgr
    100011    1   udp    871  rquotad
    100011    2   udp    871  rquotad
    100011    1   tcp    874  rquotad
    100011    2   tcp    874  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100003    2   tcp   2049  nfs
Quoted 9 lines
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100005    1   udp    886  mountd
    100005    1   tcp    889  mountd
    100005    2   udp    886  mountd
    100005    2   tcp    889  mountd
    100005    3   udp    886  mountd
    100005    3   tcp    889  mountd

<fontfamily><param>Arial</param><x-tad-smaller>Found the answer...

</x-tad-smaller><bold><x-tad-smaller>

</x-tad-smaller><x-tad-smaller>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126263</x-tad-smaller><x-tad-smaller>

</x-tad-smaller></bold></fontfamily>

On Sep 13, 2005, at 10:23 AM, Scott Leerssen wrote:

<excerpt>Thanks in advance for plowing through this message...

I have NFS built into a 2.6.13 kernel running on Fedora Core 3, and am unable to mount a filesystem on the server running the kernel. Output in /var/log/messages seems to indicate a successful mount request:

Sep 13 10:10:41 boot10-5-3-54 rpc.mountd: authenticated mount request

from 10.5.1.1:870 for /I (/I)

However the client gives me this:

mount: 10.5.3.54:/I failed, reason given by server: Permission denied

Even though from the client:

[root@devmws5 fc3mws]# showmount -e 10.5.3.54

Export list for 10.5.3.54:

/I *

I've noticed that Fedora blindly assumes that all of the nfs related kernel code will load as modules, as there are a number of module install options that won't occur (like '/bin/mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs'). I probably just missed some obscure configuration option.

Here's a list of what I have....

nfs-utils-1.0.6-52

kernel config for NFS in case it helps:

linux 2.6.13 built with NFS in the kernel as follows:

#

# Network File Systems

#

CONFIG_NFS_FS=y

CONFIG_NFS_V3=y

# CONFIG_NFS_V3_ACL is not set

CONFIG_NFS_V4=y

CONFIG_NFS_DIRECTIO=y

CONFIG_NFSD=m

CONFIG_NFSD_V3=y

# CONFIG_NFSD_V3_ACL is not set

CONFIG_NFSD_V4=y

CONFIG_NFSD_TCP=y

CONFIG_ROOT_NFS=y

CONFIG_LOCKD=y

CONFIG_LOCKD_V4=y

CONFIG_EXPORTFS=m

CONFIG_NFS_COMMON=y

CONFIG_SUNRPC=y

/etc/exports:

/R *(rw,async,hide,insecure,no_root_squash,secure_locks)

/I *(rw,async,hide,insecure,no_root_squash,secure_locks)

And, finally, output from the client:

[root@devmws5 fc3mws]# rpcinfo -p 10.5.3.54

program vers proto port

    100000    2   tcp    111  portmapper

    100000    2   udp    111  portmapper

    100024    1   udp  32768  status

    100024    1   tcp  32769  status

    100021    1   udp  32769  nlockmgr

    100021    3   udp  32769  nlockmgr

    100021    4   udp  32769  nlockmgr

    100021    1   tcp  32774  nlockmgr

    100021    3   tcp  32774  nlockmgr

    100021    4   tcp  32774  nlockmgr

    100011    1   udp    871  rquotad

    100011    2   udp    871  rquotad

    100011    1   tcp    874  rquotad

    100011    2   tcp    874  rquotad

    100003    2   udp   2049  nfs

    100003    3   udp   2049  nfs

    100003    4   udp   2049  nfs

    100003    2   tcp   2049  nfs

    100003    3   tcp   2049  nfs

    100003    4   tcp   2049  nfs

    100005    1   udp    886  mountd

    100005    1   tcp    889  mountd

    100005    2   udp    886  mountd

    100005    2   tcp    889  mountd

    100005    3   udp    886  mountd

    100005    3   tcp    889  mountd

and from the server:

[root@boot10-5-3-54 ~]# rpcinfo -p localhost

program vers proto port

    100000    2   tcp    111  portmapper

    100000    2   udp    111  portmapper

    100024    1   udp  32768  status

    100024    1   tcp  32769  status

    100021    1   udp  32769  nlockmgr

    100021    3   udp  32769  nlockmgr

    100021    4   udp  32769  nlockmgr

    100021    1   tcp  32774  nlockmgr

    100021    3   tcp  32774  nlockmgr

    100021    4   tcp  32774  nlockmgr

    100011    1   udp    871  rquotad

    100011    2   udp    871  rquotad

    100011    1   tcp    874  rquotad

    100011    2   tcp    874  rquotad

    100003    2   udp   2049  nfs

    100003    3   udp   2049  nfs

    100003    4   udp   2049  nfs

    100003    2   tcp   2049  nfs

    100003    3   tcp   2049  nfs

    100003    4   tcp   2049  nfs

    100005    1   udp    886  mountd

    100005    1   tcp    889  mountd

    100005    2   udp    886  mountd

    100005    2   tcp    889  mountd

    100005    3   udp    886  mountd

    100005    3   tcp    889  mountd

</excerpt>