NFS mount (Ubuntu) fails after installation of 9.10-STABLE 201605021851

[SmilingInSeattle]

Just reverted back to 9.10-STABLE-201604261518 after the fstab NFS mount (and a Command Line NFS mount) from my Ubuntu 16.04 workstation to my freenas server failed after the GUI installation of 9.10-STABLE-201605021851.

Did I uncover a bug, did I get a bad GUI installation, or are there new permission requirements? I saw no error messages on the server after it rebooted.

 

[SmilingInSeattle]

I sould add, because I know it will be asked,

fstab entry is:

#NFS mount to NASbox
192.168.1.10:/mnt/nas /mnt nfs _netdev,rw,hard,intr 0 0

and the CLI was simply:

>sudo mount 192.168.1.10:/mnt/nas /mnt

Thinking beforehand that it could be a permission problem I changed the permission for /mnt/nas from 757 to 777 (owner is 1000 and group is 100) for /mnt/nas/data which is where I want to go to, but owner is root and group is wheel for /mnt and /mnt/nas on my freenas server.

 

[styno]

Can you run 'showmount -e <nasip> from the Linux box for both Freenas versions? And maybe also 'exportfs' from the Freenas box?

 

[SmilingInSeattle]

[SOLVED]

From FREENAS9.10-STABLE-201604261518

[dixon@freenas ~]$ showmount -e
Exports list on localhost:
/mnt/nas 192.168.1.0

>cat mounts
/mnt/nas -alldirs -network 192.168.1.0/24

After rebooting back into FREENAS9.10-STABLE-201605021851

[dixon@freenas ~]$ showmount -e
Exports list on localhost:
/mnt/nas 192.168.1.0

[root@freenas /etc]# cat exports
/mnt/nas -alldirs -network 192.168.1.0/24

and I was able to access my shares!

Shows that glitches sometimes happen. Before making this post I'd rebooted 2016050021851, but it still came up unable to attach the NFS shares. Only by reverting back a release, then reactivating the newest release was the problem solved; hnowever I thing I'll hold on to the 20160426 release for a couple more successful new releases.