NFS mount between two 10.04 LTS systems fails

Asked by Jyri

NFS mount from 32bit 10.04 LTS systems acting as server to 64bit 10.04 LTS acting as client fails with following errors:
From client I see:
# sudo mount /media/data0
mount.nfs: access denied by server while mounting 10.1.1.1:/media/data0

From servers syslog I see:
Nov 21 14:11:19 tanelorn mountd[1714]: authenticated mount request from 10.1.1.2:745 for /media/data0 (/media/data0)
Nov 21 14:11:19 tanelorn mountd[1714]: qword_eol: fflush failed: errno 2 (No such file or directory)

This used to work. Probably some of the late updates has broken it.

Is there already a but report about this?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu util-linux Edit question
Assignee:
No assignee Edit question
Solved by:
Jyri
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Can you give the output of:

cat /etc/fstab

You kinda forgot that and it's massively important as it contains the settings for the mount, which we currently don't know.

Revision history for this message
Jyri (oku-iki) said :
#2

Sure, here is the relevant entry:
10.1.1.1:/media/data0 /media/data0 nfs noauto,wsize=32768,rsize=32768,intr,bg 0 0

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3
Revision history for this message
Jyri (oku-iki) said :
#4

Well, know how to operate NFS, I have been doing that for 15 years. It also does not appear that my problem is with the client, but with the server so the link you posted really does not help. BTW, the relevant line of my /etc/exports on server end is:
/media/data0 10.1.1.2(rw,no_subtree_check,no_root_squash)

The setup I am using has been working since Ubuntu 8 and it used to work also on 10.04 LTS before now, but some updates during past couple of months probably broke it, since nothing else has changed.

I think the most important piece if information here is:
Nov 21 14:11:19 tanelorn mountd[1714]: qword_eol: fflush failed: errno 2 (No such file or directory)

But I have no idea what it means.

I was just wondering if this problem is already know or should I make a bug report about it. Apparently I need to learn how to use Apport.

This gentoo bug appears to describe a similar problem, unfortunately it does not describe solution or work around:
http://bugs.gentoo.org/show_bug.cgi?format=multiple&id=330799

Fortunately samba still works. It just feels a bit stupid the share disk between two Linux boxes with samba.

Revision history for this message
Jyri (oku-iki) said :
#5

This is really weird indeed. I was about to make the bug report about this incident, but when I tried to reproduce the problem the mount just worked. I did not change anything, I didn't boot either of the systems, even the PID of mountd was still the same as when I had the problem.

Anyway nfs mounting works now, so I guess the problem is solved.

Revision history for this message
L. POUZENC (lpouzenc) said :
#6

Hi,

I have the same error message this morning. My NFS server is on a MSI netbook U100Plus, running an up-to-date 10.10 Ubuntu. uname says :
Linux lud-msi 2.6.35-30-generic #61-Ubuntu SMP Tue Oct 11 15:29:15 UTC 2011 i686 GNU/Linux

My NfS client is an ARM based board : Technexion TAM3517 + Twister. I use NFS for disk-less booting a debian with a 2.6.32 kernel from Technexion, based on TI's work for adding custom drivers for this hardware.
Source of the used kernel on the client side are here :
http://www.technexion.com/index.php/support-center/downloads/ti-cpu-modules/tam-3517/546-xuk-src-tar/download
I can give config file and compiler details if necessary but I hope that the problem is server-side.

On th ARM board, I can see a kernel Panic because VFS cannot mount my NFS mount point just after a mount error message that says "Error -13".

Network between client and server is 2 home 8-ports non-configurable switchs @100Mbits.
Client IP is static : 192.168.1.5
Server IP is static : 192.168.1.4 but configured by hand AFTER the boot (and after nfs services start), as eth0:0.

My /etc/exports (on server) contains only one uncommented line :
/nfsroot/angstrom 192.168.1.5(rw,sync,no_subtree_check,no_root_squash)

This path "/nfsroot/angstrom" on the server is actually an empty folder in the root fs because I mount manually an rootfs image (with mount -o loop) when I work on my board. This mount is also done AFTER nfs services starts. (Could be a cause ?)

This configuration and process has worked 50 or 80 times in the last weeks without any problem : my ARM board boots just fine.

On the netbook (server), packages around the mess :

# dpkg-query -s nfs-kernel-server
Package: nfs-kernel-server
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 396
Maintainer: Ubuntu Developers <email address hidden>
Architecture: i386
Source: nfs-utils
Version: 1:1.2.2-1ubuntu1.2

dpkg-query -s nfs-kernel-server
Package: nfs-kernel-server
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 396
Maintainer: Ubuntu Developers <email address hidden>
Architecture: i386
Source: nfs-utils
Version: 1:1.2.2-1ubuntu1.2

When I have encountred the bug for the fisrt time, I have seen it on the client screen (ARM board). I have first tried to reboot the board twice (may be a network problem in my mind). And the problem was exactly the same from the pointn of view of the client : NFS error -13 ; NFs error -13.

Okay. I have check server's log and see in daemon.log :

Oct 30 11:43:29 lud-msi mountd[1228]: authenticated mount request from 192.168.1.5:820 for /nfsroot/angstrom (/nfsroot/angstrom)
Oct 30 11:43:29 lud-msi mountd[1228]: qword_eol: fflush failed: errno 2 (No such file or directory)
Oct 30 11:46:03 lud-msi mountd[1228]: authenticated mount request from 192.168.1.5:820 for /nfsroot/angstrom (/nfsroot/angstrom)
Oct 30 11:46:03 lud-msi mountd[1228]: qword_eol: fflush failed: errno 2 (No such file or directory)

I have done a simple :
# /etc/init.d/nfs-kernel-server restart
and then a reset of my ARM board, and since that action, everything is fine.

In the servers logs, I can see mountd messages without errors :

Oct 30 12:29:35 lud-msi mountd[2430]: authenticated mount request from 192.168.1.5:696 for /nfsroot/angstrom (/nfsroot/angstrom)
Oct 30 12:41:27 lud-msi mountd[2430]: authenticated mount request from 192.168.1.5:820 for /nfsroot/angstrom (/nfsroot/angstrom)

Hope those informations will help to troobleshot this bug...

Ludovic Pouzenc