Modify

Opened 5 years ago

Last modified 3 years ago

#12935 accepted defect

nfs mount failed

Reported by: vovan@… Owned by: florian
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

I have earlier versions working fine, but recently mounting of nfs shares failed:
mount.nfs -vvv -o nolock nfs.net.home:/mnt/diskless/install /mnt/torrents
mount.nfs: timeout set for Sat Feb 2 15:52:02 2013
mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.1.219,clientaddr=192.168.1.253'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,addr=192.168.1.219'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.219 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.219 prog 100005 vers 3 prot UDP port 32767
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported

Unfortunately the last working image I have is relatively old (r30950).

Attachments (0)

Change History (16)

comment:1 Changed 5 years ago by darkman

having same problem!

comment:2 Changed 5 years ago by anonymous

Same problem on a WRT54GL here with latest trunk.
"Protocol not supported" even though I selected, compiled and installed everything nfs-related (except server-related things like kmod-nfs-server).

comment:3 Changed 5 years ago by Luke McKee <hojuruku@…>

did you guys enable busybox (when making an image) to support nfs shares?

comment:4 Changed 5 years ago by tomaszg@…

I had the same problem. Changing busybox options or nfs-utils didn't change a thing. It was kernel that reported "Protocol not supported". Of course, I had kernel nfs module loaded.

However, when I entered kernel_menuconfig and hard-compiled nfs-client support into kernel - magically it started to work.

comment:5 follow-up: Changed 5 years ago by anonymous

Same issue here

comment:6 in reply to: ↑ 5 Changed 5 years ago by anonymous

Same with the latest Barrier Breaker here

doing just the nfs-client support check in kernel_menuconfig did not help and actually broke the nfs support packages - they became empty ...

comment:7 Changed 4 years ago by Matthew M. Dean

Still happens on r37806 will try a kernel menuconfig

comment:8 Changed 4 years ago by Matthew M. Dean

doing kernel menuconfig and adding the nfs options built-in has resolved this issue.

comment:9 Changed 4 years ago by anonymous D

come on.. this problem lasts forever

comment:10 Changed 4 years ago by florian

  • Owner changed from developers to florian
  • Status changed from new to accepted

comment:11 Changed 4 years ago by oflameo2@…

I am reporting the same problem.

comment:12 Changed 4 years ago by anonymous

Reporting same issue with r39319

comment:13 Changed 4 years ago by anonymous

The underlying reason is most likely a missing nfsv3.ko. I've copied it manually from the build tree and NFS mounts now work as they should. Either adding nfsv3.ko to the NFS target in package/kernel/linux/modules/fs.mk or defining and enabling a separate NFS3 target would solve the problem.

comment:14 Changed 4 years ago by anonymous

nfsv3.ko will be included in trunk builds after r39459. This change might fix things.

comment:15 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:16 Changed 3 years ago by florian

Is that still an issue in barrier breaker and trunk?

Add Comment

Modify Ticket

Action
as accepted .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.