l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
September 2: Social Gathering
Next Installfest:
Sat. Sept. 27, 10am-6pm
Latest News:
Aug. 30: September Installfest scheduled
Page last updated:
2004 Dec 04 10:53
Events
 Meetings
 Installfests
 Demos
 Photos
Services
 Library
 LERT
 Jobs
 Documents
Interact
 Mailing Lists
 - Search
 - Archives
 Chat
About Us
 Members
 Projects
 Testimonials
 Call for Speakers
 Why Not MS?
 Finances
 Sponsors

^Home
?Search
?News & RSS
?Calendar
@Contact Us
$Buy Stuff
=Printable


The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] NFS Mounting Error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] NFS Mounting Error




Hello,

I am trying to mount a NFS volume where both machines are on the same home network, but I get the following errors. From the client:

[root@pinky mnt]# mount -t nfs 192.168.0.14:/tmp /mnt/tmp
mount: 192.168.0.14:/tmp failed, reason given by server: Permission denied

On the server:

cruncher:/# tail /var/log/syslog
[...]
Dec 4 10:30:31 cruncher rpc.mountd: authenticated mount request from 192.168.0.2:773 for /tmp (/tmp)
Dec 4 10:30:31 cruncher rpc.mountd: getfh failed: No such device

I haven't been able to find a single report of this type of syslog error. The server has a custom kernel, version 2.6.8, with the NFS server as a loadable module, and runs debian testing. Two different clients, with different kernels and different distros, gave the same error. Exports looks like:

cruncher:/# more /etc/exports
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/var/cache/apt/archives 192.168.0.0/255.255.255.0(ro)
/tmp 192.168.0.2(sync,no_root_squash)

but exportfs -ra gives:

cruncher:/# exportfs -ra
exportfs: /etc/exports [3]: No 'sync' or 'async' option specified for export "192.168.0.0/255.255.255.0:/var/cache/apt/archives".
Assuming default behaviour ('sync').
NOTE: this default has changed from previous versions
192.168.0.2:/var/cache/apt/archives: No such device
192.168.0.2:/tmp: No such device

Restarting portmap, rpc.mountd, rpc.nfsd, rpc.statd and rpc.lockd don't correct the error. rpcinfo gives:

cruncher:/# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 820 mountd
100005 1 tcp 823 mountd
100005 2 udp 820 mountd
100005 2 tcp 823 mountd
100005 3 udp 820 mountd
100005 3 tcp 823 mountd
100024 1 udp 826 status
100024 1 tcp 829 status

I don't know why nfsd doesn't show up. nfs-common and nfs-kernel-server are both installed on the server. Any ideas or suggestions would be most welcome.

Thanks,

Chris
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

CD Burns Wanted!

LUGOD: Linux Users' Group of Davis
1105 Kennedy Place, Suite 1, Davis, CA 95616
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Marc Hall
For a generous donation to allow us to continue meeting at the Davis Library.