You are not logged in.

#1 2014-04-29 16:01:32

donpicoro
Member
Registered: 2009-04-10
Posts: 42

NFS 'not a directory' error

Hello fellows,

I have setup a server that need to do some PXEBOOTING with RARP and NFS...

Booting with tftp... check.
Getting the proper kernel based on the MAC -> RARP -> IP ... checked.
NFS to mount the system ... failed.

It used to work a few weeks ago and now suddenly is failing consistently and the error messages I get from the booting machines are just "Not a directory". And I assure you they are both directories. As I told you, it used to work a couple of weeks ago.

The system I try to boot is LynxOS and it was a headache to realize the need for NFSv2 and I am sure I am running v2 (ONLY v2 both NFSD and MOUNTD).

Has anyone encountered this kind of problem recently/before/at all?

ANY input will be GREATLY appreciated.

Offline

#2 2014-04-30 09:12:41

Rexilion
Member
Registered: 2013-12-23
Posts: 784

Re: NFS 'not a directory' error

Did you update your nfsd-utils lately? (check /var/log/pacman.log).


fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

Offline

#3 2014-04-30 13:27:31

donpicoro
Member
Registered: 2009-04-10
Posts: 42

Re: NFS 'not a directory' error

Hello Rexilion.

No, no updates when it comes to that... nfs-utils was updated on January. rpcbind is from September last year.

As an update I can reproduce the same behaviour between two Archlinux boxes when I try to mount it with NFSv2

mount.nfs: timeout set for Wed Apr 30 15:27:15 2014
mount.nfs: trying text-based options 'nfsvers=2,addr=xxx.xxx.xx.xxx'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying xxx.xxx.xxx.xxx prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying xxx.xxx.xxx.xxx prog 100005 vers 1 prot UDP port 20048
mount.nfs: mount(2): Not a directory
mount.nfs: mount point /home/user/tst_nfs is not a directory

I edited the IP addresses as they are public =P.

When I use nfsvers=3 instead it simply mounts like a champ.
Any further ideas?

EDIT: Yes, NFSv2 is enabled on the server ;-)

cat /proc/fs/nfsd/versions
+2 +3 +4 +4.1 -4.2

Last edited by donpicoro (2014-04-30 13:40:46)

Offline

#4 2014-04-30 13:45:37

alphaniner
Member
From: Ancapistan
Registered: 2010-07-12
Posts: 2,810

Re: NFS 'not a directory' error

LMG[nfs v2 "not a directory"]FY tongue

Last edited by alphaniner (2014-04-30 13:47:38)


But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner

Offline

#5 2014-04-30 15:24:06

donpicoro
Member
Registered: 2009-04-10
Posts: 42

Re: NFS 'not a directory' error

hehe I know... I have ended up there all day. And I have two things to say:

1) the Archlinux package is flagged as out-of-date anyways ;-)

2) I swear to cow it worked three weeks ago. I had to reboot the server and I have no idea what changed in between. Maybe I got it to work after a long struggle when I learned I had to activate NFSv2 and whatnot.

How shall I know NFS version is installed? the nfs-utils package has a version which looks very much unrelated to anything.

Offline

Board footer

Powered by FluxBB