rkulagow Posted January 8, 2016 Share Posted January 8, 2016 unRaid 6.1.6, Mythbuntu 14.04.03 Can't seem to get it to work. On unRaid, I have: root@Tower:~# showmount -e Export list for Tower: /mnt/user/test * # cat /etc/exports # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. "/mnt/user/test" -async,no_subtree_check,fsid=100 *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) But mounting on the MythBuntu side presents: # mount -t nfs4 -o user=guest,proto=tcp,port=2049 tower.local:/test t mount.nfs4: Protocol not supported Same for: mount -t nfs4 -o user=guest,proto=tcp,port=2049 tower.local:/mnt/user/test t mount.nfs4: Protocol not supported But nfsv3 works: mount -t nfs -o user=guest tower.local:/mnt/user/test t Am I doing something incorrect on the unRaid or MythBuntu host? Quote Link to comment
PeterB Posted January 8, 2016 Share Posted January 8, 2016 As far as I am aware, unRAID still does not support nfs v4, which is a shame because I understand that v4 should be more robust and show improved performance. I'm not sure what needs to be done to enable v4 support. Quote Link to comment
rkulagow Posted January 8, 2016 Author Share Posted January 8, 2016 Thanks. But according to this: http://lime-technology.com/wiki/index.php/UnRAID_Manual_6#NFS_.28Network_File_System.29 There should already be NFSv4 available? I'm not seeing where I should be able to update a share for NFSv4 Quote Link to comment
PeterB Posted January 9, 2016 Share Posted January 9, 2016 It would seem that the writer of that manual is not running the same version of unRAID as we, mere mortals, have access to! Quote Link to comment
Squid Posted January 9, 2016 Share Posted January 9, 2016 It would seem that the writer of that manual is not running the same version of unRAID as we, mere mortals, have access to! except that This page was last modified on 7 July 2015, at 17:32 Quote Link to comment
BobPhoenix Posted January 9, 2016 Share Posted January 9, 2016 It would seem that the writer of that manual is not running the same version of unRAID as we, mere mortals, have access to! When I run "nfsstat -o all -234" on unRAID 6.1.6 I get: Server packet stats: packets udp tcp tcpconn 0 0 0 0 Server rpc stats: calls badcalls badclnt badauth xdrcall 0 0 0 0 0 Server reply cache: hits misses nocache 0 0 0 Server file handle cache: lookup anon ncachedir ncachedir stale 0 0 0 0 0 Server nfs v2: null getattr setattr root lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcache write create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlink mkdir rmdir readdir fsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Server nfs v3: null getattr setattr lookup access readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read write create mkdir symlink mknod 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% fsstat fsinfo pathconf commit 0 0% 0 0% 0 0% 0 0% Server nfs v4: null compound 0 0% 0 0% Server nfs v4 operations: op0-unused op1-unused op2-future access close commit 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% create delegpurge delegreturn getattr getfh link 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% lock lockt locku lookup lookup_root nverify 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% open openattr open_conf open_dgrd putfh putpubfh 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% putrootfh read readdir readlink remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% renew restorefh savefh secinfo setattr setcltid 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% setcltidconf verify write rellockowner bc_ctl bind_conn 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% exchange_id create_ses destroy_ses free_stateid getdirdeleg getdevinfo 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% getdevlist layoutcommit layoutget layoutreturn secinfononam sequence 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% set_ssv test_stateid want_deleg destroy_clid reclaim_comp 0 0% 0 0% 0 0% 0 0% 0 0% Client packet stats: packets udp tcp tcpconn 0 0 0 0 Client rpc stats: calls retrans authrefrsh 0 0 0 Client nfs v2: null getattr setattr root lookup readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read wrcache write create remove rename 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% link symlink mkdir rmdir readdir fsstat 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% Client nfs v3: null getattr setattr lookup access readlink 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% read write create mkdir symlink mknod 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% fsstat fsinfo pathconf commit 0 0% 0 0% 0 0% 0 0% Client nfs v4: null read write commit open open_conf 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% open_noat open_dgrd close setattr fsinfo renew 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% setclntid confirm lock lockt locku access 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% getattr lookup lookup_root remove rename link 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% symlink create pathconf statfs readlink readdir 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% server_caps delegreturn getacl setacl fs_locations rel_lkowner 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% secinfo exchange_id create_ses destroy_ses sequence get_lease_t 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% reclaim_comp layoutget getdevinfo layoutcommit layoutreturn getdevlist 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% (null) 0 0% Which mentions V4 so it looks like NFS v4 is supported to me. Of course I don't understand what it is displaying so could be wrong too! Quote Link to comment
rkulagow Posted January 9, 2016 Author Share Posted January 9, 2016 Right, which why I'm confused about why I can't mount nfs4. Hopefully, someone who does have it working will just say, you're doing it wrong, dummy, and post the config on the unRaid side, and how they're mounting on the Ubuntu side, and then we're done. Quote Link to comment
PeterB Posted January 9, 2016 Share Posted January 9, 2016 The nfs build may well include v4 functionality, but there are further requirements in order to implemet v4. It seems that Slackware has a history of not enabling v4 by default - see here. On my unRAID server (v6.1.6), I am unable to find any of the libraries which are mentioned in that thread as being required for nfs v4 support. In particular, "find /usr -name *gss*" pulls up some samba libraries, but nothing for nfs. Like you, I hope that I am wrong and someone will pop up and tell us that nfs v4 is working and that you just have to do x, y and z ..... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.