[SOLVED] OpenSUSE NFS mount permission denied

[r00ps]

Hi all,

I'm trying to mount an NFS share on my TS210 with the latest firmware using OpenSUSE 11.3 and I keep getting access denied errors:

Code: Select all

mount.nfs: access denied by server while mounting w.x.y.z:/share

I'm trying to set up an automatic mount in /etc/fstab with the line:

Code: Select all

w.x.y.z:/share     /path-to/share      nfs     defaults 0 0

I have also tried 'nfsvers=3,user,auto' instead of defaults for the options after finding a few posts about it but to no avail. I have given the share 'no limits' access rights and tried several things in the allowed IP address list:

Code: Select all

a.b.c.d
a.b.c.0/255.255.255.0
*

I can see the share using the showmount command:

Code: Select all

showmount -e w.x.y.z
Export list for w.x.y.z:
/share                 
/Qweb                   
/Qusb                   
/Qrecordings           
/Qmultimedia           
/Qdownload             
/Public                 
/Network Recycle Bin 1 


I'm guessing its something to do with user authentication but can't seem to figure out what to try next? I know my way around linux a bit but am not really that familiar with NFS configuration.

Cheers!

rupert

[schumaku]

Assuming there is no NFS Access Control limitaiton in place on a per-share base (Access Right Management >> Share Folders -> [Share] -> Action ->[NFS Access Control])...:

Answered many times for several Linux distributions: You must explicitly enforce nfsv3, the actual NAS frimware appears to support nfsv4, but this is not fully activated yet. thus you get the permission denied.

[r00ps]

Hi,

Thanks for the reply, I've seen some of the other threads and I tried setting the 'nfsvers=3' option in fstab, I'll keep that in now but it still doesn't mount? The line is fstab for the mount is currently:

w.x.y.z:/share <mount point> nfs nfsvers=3 0 0

I've just double checked the share's access rights and they are set to 'No Limit' and currently the allowed IP address range is set to '192.168.1.0/255.255.255.0'. My home LAN is 192.168.1.xxx.

Cheers,

rupert

[schumaku]

Stragne. Start without an address limitation - the effect on a closed LAN and allowing the full subnet is limited anyway.

[r00ps]

Hi,

I've changed the Allowed IP Address to * and it's still denying access...it was set like that as that was the last thing I was trying before posting here

Cheers

rupert

[r00ps]

Hi,

I've been away for a bit but back now and looking at this problem again. If I use the 'verbose' option for the mount command I get:

mount.nfs: timeout set for Tue Apr 19 09:29:57 2011
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.99 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.99 prog 100005 vers 3 prot UDP port 52808
mount.nfs: trying text-based options 'addr=192.168.1.99,vers=3,proto=tcp,mountvers=3,mountproto=udp,mountport=52808'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting qnap:/share

my fstab line is:

qnap:/share /home/rupert/share nfs nfsvers=3 0 0

I have found that if I change the fstab line to access the 'Public' built-in share it works! I've been through the permissions for my 'share' share and can't see any difference between it and the Public share, other than that it's not built-in? Any more ideas?

Cheers,

rups

[schumaku]

Strange, still....

What says the NAS' dmesg ?

[~] # dmesg
...

What NAS firmware version in place?

[tmt]

qnap:/share /home/rupert/share nfs nfsvers=3 0 0

You're trying to mount the "/share" directory. This isn't going to work, since /share isn't exported.

You need to mount the individual shares, i.e. the exported directories in /share itself

[r00ps]

@tmt

I've created a new shared directory called 'share' ( I wasn't feeling very creative ). The new share is available to mount according to the output from showmount -e:

Code: Select all

Export list for qnap:
/share                 
/Qweb                   
/Qusb                   
/Qrecordings           
/Qmultimedia           
/Qdownload             
/Public                 
/Network Recycle Bin 1 

@schumaku

I just updated to the latest firmware, 3.4.2 Build0331, and the problem remains.

Here's my dmesg output:

Code: Select all

 TB/1.81 TiB)
sd 0:0:0:0: [sda] 0-byte physical blocks
Check proc_name[mvSata].
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: [sdb] 0-byte physical blocks
sd 0:0:0:0: Attached scsi generic sg0 type 0
Check proc_name[mvSata].
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 23 00 10 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
SPI Serial flash detected @ 0xf4000000, 16384KB (64sec x 256KB)
Creating 6 MTD partitions on "spi_flash":
0x000000000000-0x000000080000 : "U-Boot"
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
0x000000200000-0x000000400000 : "Kernel"
 sdb:
0x000000400000-0x000000d00000 : "RootFS"
0x000000d00000-0x000001000000 : "RootFS2"
 sda:
0x000000080000-0x0000000c0000 : "U-Boot Config"
0x0000000c0000-0x000000200000 : "NAS Config"
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o 1 Giga ports supported
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload (TSO) supported
  o Large Receive offload (LRO) supported
  o Receive checksum offload supported
  o Transmit checksum offload supported
  o Network Fast Processing (Routing) supported - (Disabled)
  o Proc tool API enabled
  o SKB Reuse supported - (Disabled)
  o SKB Recycle supported - (Disabled)
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
    o  register under mv88fx_eth platform
 sdb1 sdb2 sdb3 sdb4
 sda1 sda2 sda3 sda4
    o eth0, ifindex = 2, GbE port = 0

mvFpRuleDb (00000010): 0 entries, 0 bytes
Marvell debug tracing is on
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 1:0:0:0: [sdb] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] Attached SCSI disk
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
sd 1:0:0:0: [sdb] Attached SCSI disk
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb: create proc systemp successfully
usb: create proc systemp successfully
mice: PS/2 mouse device common for all mice
md: raid1 personality registered for level 1
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
TCP cubic registered
NET: Registered protocol family 17
rtc kw_rtc: setting system clock to 2011-04-20 08:39:57 UTC (1303288797)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: gzip image found at block 0
usb 1-1: new high speed USB device using ehci_marvell and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 136K
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): mounted filesystem with writeback data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb1): mounted filesystem with writeback data mode
md: md9 stopped.
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md9 active with 2 out of 2 mirrors
md9: bitmap initialized from disk: read 5/5 pages, set 0 bits
created bitmap (65 pages) for device md9
md9: detected capacity change from 0 to 542769152
 md9: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: md13 stopped.
md: bind<sdb4>
md: bind<sda4>
raid1: raid set md13 active with 2 out of 2 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
 md13: unknown partition table
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md13): using internal journal
EXT3-fs (md13): mounted filesystem with writeback data mode
fuse init (API version 7.13)
NET: Registered protocol family 5
md: linear personality registered for level -1
md: raid0 personality registered for level 0
device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver usblp
sysinfo: Module loaded.
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver U82 (Mar 31 2011 03:21:53)  LBD=OFF with ioctl loaded at bf17e000
NTFS read/write support included
Hfs+/HfsX read/write support included
Slow work thread pool: Starting up
Slow work thread pool: Ready
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
Enable WDT...
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver snd-usb-caiaq
eth0: mac address changed
eth0: link down
eth0: started
eth0: link up, full duplex, speed 100 Mbps
kjournald starting.  Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: bind<sda2>
raid1: raid set md2 active with 1 out of 1 mirrors
md2: detected capacity change from 0 to 542769152
 md2: unknown partition table
Adding 530040k swap on /dev/md2.  Priority:-1 extents:1 across:530040k
md: bind<sdb2>
RAID1 conf printout:
 --- wd:1 rd:2
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:1, o:1, dev:sdb2
md: recovery of RAID array md2
md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: Recovering started: md2
md: using 128k window, over a total of 530048 blocks.
active port 0 :139
active port 1 :445
active port 2 :20
md: md2: recovery done.
md: Recovering done: md2, degraded=1
RAID1 conf printout:
 --- wd:2 rd:2
 disk 0, wo:0, o:1, dev:sda2
 disk 1, wo:0, o:1, dev:sdb2
md: md0 stopped.
md: md0 stopped.
md: md0 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 1998792294400
 md0: unknown partition table
EXT4-fs (md0): mounted filesystem with ordered data mode
eth0: stopped
eth0: link down
eth0: started
eth0: stopped
eth0: started
eth0: link up, full duplex, speed 100 Mbps
active port 0 :139
active port 1 :445
active port 2 :20
warning: `proftpd' uses 32-bit capabilities (legacy support in use)
warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
rule type=2, num=0
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)


[r00ps]

hmm...I think I've solved this! After tmt's reply I tried creating a new shared folder with a different name, and it mounted straight away! It must be something to do with the fact that it's called 'share' and it's confusing the NFS server. The 'share' shared folder works fine for Samba and FTP, and even when getting the list of exports using 'showmount'. Oh well, live and learn

So, the moral of this story is don't use 'share' for your share name if you are using NFS!! Hope this helps out someone else...

[tmt]

Interesting! Well, the name "share" certainly isn't reserved by NFS, so I think we can conclude there is some special processing in the QNAP export checking. Sounds like a bug, frankly, but easily worked around.