NFS problem

[Lasse_kongo]

TY it also works for mediaplayer Egreat m31b

[ABATAPA]

T
I have tried:
/tmp/harddisk/part1/ 192.168.0.4(rw) (This is the dir structure)
/share 192.168.0.4(rw) (This is name of the SAMBA demo mode share)

Try

/tmp/mnt 192.168.0.4/32(rw,async,no_root_squash,anonuid=0,anongid=0)

[Andrey_3]

Use "insecure" option in /etc/exports file. For example:
/tmp/harddisk/ftp 192.168.0.2(rw,async,insecure,no_root_squash,anonuid=0,anongid=0)

[dl9sec]

Hi together,

after i managed to get my Samba running well, it seems that i now got trouble with NFS. Maybe this has to do with xinetd, because this was the last modification done before i got this message after trying to mount my usual nfs-share:

mount.nfs: access denied by server while mounting (null)

The mount should be done with:

#! /bin/bash
mount -t nfs 192.168.0.4:/tmp/harddisk /mnt/wlhdd -o rw,soft,udp,rsize=32768,wsize=32768

The /etc/exports on my WL-HDD (192.168.0.4) shows:

# automagically generated from web settings
/tmp/harddisk/ *(rw,async,no_root_squash)
/tmp/harddisk/naspics/ *(ro,async,no_root_squash)
/tmp/harddisk/nasmusic/ *(ro,async,no_root_squash)
/tmp/harddisk/nasvideo/ *(rw,async,no_root_squash)

From the client side i can see the exports:

showmount -e 192.168.0.4

Export list for 192.168.0.4:
/tmp/harddisk           *
/tmp/harddisk/nasmusic  (everyone)
/tmp/harddisk/nasvideo  (everyone)
/tmp/harddisk/naspics   (everyone)

Do i have to change any settings in xinetd.conf to make my nfs-mount work again?

Thanks in advance,

Thorsten

[dl9sec]

Solved.

It hasn't t do anything with WL-HDDs services.
On the client side something went wrong with the directories where the share should be mounted. So after unmount the obsolete mount and remount, all works fine.

Mabe the Board-Admin can delete the post because its useless...

Regards, Thorsten

[Bohlendach]

A few days ago I purchased Popcorn Hour A-110 which is a very strong and silent Media Tank. Sadly it fails to browse my SAMBA share on the WL-500g Deluxe.

Password encryption has to be set to 'Yes' in samba for a Popcorn Hour 110 to be able to browse your share.

[sgora]

Hi,
I'm using RT-N16 with firmware 1.9.2.7-rtn-r1906.

During using of NFS filesystem exported from connected via USB dysk my NFS server on RT-N16 sometimes crashes. (I have to restart nfsd end mountd deamons).
In syslog there is information:
=======================================
Aug 27 19:36:06 kernel: dentry_open called with NULL vfsmount
Aug 27 19:36:06 kernel: Call Trace:
Aug 27 19:36:06 kernel: [<8000de20>] dump_stack+0x8/0x34
Aug 27 19:36:06 kernel: [<80079acc>] dentry_open+0x7c/0xc8
Aug 27 19:36:06 kernel: [<c00da284>] get_name+0xcc/0x19c [exportfs]
Aug 27 19:36:06 kernel: [<c00da7e0>] find_exported_dentry+0x2d8/0x6ec [exportfs]
Aug 27 19:36:06 kernel: [<c00dac48>] export_decode_fh+0x54/0xac [exportfs]
Aug 27 19:36:06 kernel: [<c0264454>] fh_verify+0x364/0x6f4 [nfsd]
Aug 27 19:36:06 kernel: [<c02715a8>] nfsd3_proc_getattr+0xc8/0x180 [nfsd]
Aug 27 19:36:06 kernel: [<c026029c>] nfsd_dispatch+0xbc/0x2ac [nfsd]
Aug 27 19:36:06 kernel: [<c01f207c>] svc_process+0x500/0x964 [sunrpc]
Aug 27 19:36:07 kernel: dentry_open called with NULL vfsmount
Aug 27 19:36:07 kernel: Call Trace:
=======================================
Does anyone know some fix for nfs ?

[verjikd]

I am having problems with the NFS-server on my RT-16N, using an Oleg firmware of this july. It stalls when copying a lot of files from one of the attached USB drives. An error 521 and something like cannot find files.
I see only a few references on google on this (kernel problem). However I am wondering whether the mount options might cause a problem; much more people should have problems. What options do you use?

[verjikd]

More info. I have problems mounting with this command:
mount -t nfs -o vers=3,tcp,lock,intr,hard,rw 192.168.123.1:/mnt/nfs-data /Asus

The error I get when copying a large amount of files from the Asus to my Kubuntu 10.04 PC (by dmesg through telnet): dentry_open called with NULL vfsmount
Call Trace:
[<8000de20>] dump_stack+0x8/0x34
[<80079eec>] dentry_open+0x7c/0xc8
[<c00da284>] get_name+0xcc/0x19c [exportfs]
[<c00da77c>] find_exported_dentry+0x274/0x6ec [exportfs]
[<c00dac48>] export_decode_fh+0x54/0xac [exportfs]
[<c01bb454>] fh_verify+0x364/0x6f4 [nfsd]
[<c01c8598>] nfsd3_proc_getattr+0xc8/0x180 [nfsd]
[<c01b729c>] nfsd_dispatch+0xbc/0x2ac [nfsd]
[<c024807c>] svc_process+0x500/0x964 [sunrpc]
[<c01b7b90>] nfsd+0x224/0x460 [nfsd]
[<8000a05c>] kernel_thread_helper+0x10/0x18

NFS stalls for a minute than resumes working, though filecopying must start again.

My (unsafe) /etc/exports: /mnt *(rw,no_subtree_check,no_root_squash,sync)

I'll now try:
mount -t nfs -o hard,rw,async,noauto 192.168.123.1:/mnt/nfs-data/ /Asus

[theMIROn]

It's already fixed in svn. So, just get the latest build

[verjikd]

That's great, thanks. I was using the svn-version of July

Edited: it is fixed indeed

[Foxem]

Hi,

I have a NAS (HDD My Book World 2 Western Digital 2TB with 10/100/1000 ethernet interface) with NFS folders.
I tried to mount the NFS folders from NAS on my RT-N16 but with no success.
I added
insmod nfs.ko
mount //192.168.109.130:/NFS/temp /usr/local/mnt/temp
I would appreciate it, if someone could help me with some suggestions.



Many thanks

[verjikd]

I've updated my RT-16n with the latest OLEG-firmware of 3th of July. Now I am having trouble to get the NFS-server on my RT-16n to work for all clients. The following command works from Opensuse and my Wetab: sudo mount -t nfs -o vers=3,tcp,lock,intr,hard,rw,nolock 192.168.123.1:/mnt/nfs-data/ /Asus
In syslog.log: mountd[365]: authenticated mount request from 192.168.123.103:909 for /mnt/nfs-data (/mnt/nfs-data)

However from Kubuntu 11.04 and Xubuntu 11.04 I get on the client side: mount.nfs: access denied by server while mounting 192.168.123.1:/mnt/nfs-data/
In syslog.log:mountd[365]: refused mount request from EEElaptop for /mnt/nfs-data (/): no export entry

My only exports-line is: /mnt/nfs-data 192.168.123.*(rw,async,insecure)

Why the ubuntu-variants won't connect, is beyond me.
Anyone an idea?

[verjikd]

I found it. The error has to do with the Asus RT-16N router not being able to resolve the IP address of both PC's. For both PC's were I had created fixed IP addresses for their MAC-addresses in the Asus router, with an earlier firmware version.

After updating the firmware of the router this caused the problem, although it gave both PC's the right IP address. Removing both fixed IP addresses made it working again. It is more or less a bug in the OLEG-firmware of the RT-16N (and other WL500-routers with the same kind of firmware).

Glad I found it :P

[verjikd]

And in the end it wasn't the Asus router after all, as one PC continued to have a problem. It needed to have these options to run:

mount -t nfs -o vers=3,tcp,nolock,intr,hard,rw,noauto 192.168.123.1:/mnt/nfs-data/ /Asus