Invalid export entry in /etc/exports

[TMtina]

I am having this exact problem. I'm running on a brand new F8 SSD. Latest software 6.0.353-00158.

In my case, I didn't do a restore, I removed my existing shares/volumes/pool to recreate as a new pool. After doing so, I now have this invalid entry in my exports and am unable to mount anything NFS on the new shares on the new volumes in the new pool. It's not a restore file problem, it's a coding problem somewhere.

cat /etc/exports; echo;

"" *(rw,async,insecure_locks,sec=sys,no_root_squash,anonuid=6,anongid=4)
"/Volume2/nfs-nvme-btrfs" 10.100.200.0/24(rw,async,crossmnt,insecure,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"/Volume1/nfs-nvme-ext4" 10.100.200.0/24(rw,async,crossmnt,insecure,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"/Volume1/public" *(ro,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)

I have 30 days to return this device. Hope it gets fixed quickly. I can remove the invalid entry, but as soon as the system decides to rewrite the exports via an apply to the shares, bye bye working config. Can't have this!

This issue will be resolved in future TOS versions. Please keep an eye on the update notifications.

[bugacha]

This still not fixed in TOS 6.0.555

[Gremlin]

Can I ask which protocol you have set in NFS and any other settings in advanced?
I don't normally use NFS, but I have it enabled and I don't see the issue you reported.

[bugacha]

Can I ask which protocol you have set in NFS and any other settings in advanced?
I don't normally use NFS, but I have it enabled and I don't see the issue you reported.

I believe the issue happens only when you re-install TOS from one NVMe to another one.

It basically detects old volumes but clearly with a wrong name hence

Code: Select all

""

its nothing to do with NFS

They have a binary that auto-create exports file based on TOS config

Code: Select all

/usr/sbin/allconf nfsdconf

So after re-install to a new NVMe this config gets corrupted somehow (its likely imports old volumes)

[RyanYang]

The issue has been resolved and will be included in the next version. As a temporary solution, you can execute the following command and then restart the NFS file service:

Code: Select all

tersql -sql "delete from acl_host where folder_id not in (select folder_id from share)"

[bugacha]

The issue has been resolved and will be included in the next version. As a temporary solution, you can execute the following command and then restart the NFS file service:

Code: Select all

tersql -sql "delete from acl_host where folder_id not in (select folder_id from share)"

Thank you, that did the trick !

[cadbomb]

The issue has been resolved and will be included in the next version. As a temporary solution, you can execute the following command and then restart the NFS file service:

Code: Select all

tersql -sql "delete from acl_host where folder_id not in (select folder_id from share)"

Beautiful, thanks for this!