Invalid export entry in /etc/exports

[bugacha]

After re-installing TOS6 and restoring system configuration, I noticed NFS mount stopped working

First entry in exports file is corrupt, no idea where its coming from

Code: Select all

# cat /etc/exports


"" *(rw,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"/Volume2/video" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"/Volume2/music" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"/Volume2/photos" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,all_squash,anonuid=0,anongid=997)

[TMzethar]

We will verify the problem you mentioned. If it is confirmed to exist, we will fix it in a future version.

[bugacha]

We will verify the problem you mentioned. If it is confirmed to exist, we will fix it in a future version.

Any luck finding it ?

[bugacha]

I'm asking because after manual fix of the file, it gets reverted back to have that bogus entry every day which kills NFS server. All clients that mount from NAS stop working

[bugacha]

Looks like /etc/exports is generated by /usr/sbin/allconf nfsdconf

But I cant find where its called from yet

[TMeric]

We are still continuing to validate the issue you mentioned, please stay tuned.

[bugacha]

We are still continuing to validate the issue you mentioned, please stay tuned.

This got even worse after 2nd restore to a new NVMe. I think the problem is in your Restore config scripts.

Have now 2 sets of invalid entries :

Code: Select all

"" *(rw,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)

"" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)
"" 192.168.1.0/24(rw,async,crossmnt,insecure_locks,sec=sys,all_squash,anonuid=0,anongid=997)

"/Volume2/photos" 192.168.1.0/24(rw,async,crossmnt,insecure_locks,sec=sys,all_squash,anonuid=0,anongid=997)
"/Volume2/music" 192.168.1.0/24(ro,async,crossmnt,insecure_locks,sec=sys,no_root_squash,anonuid=1001,anongid=997)

[Gremlin]

I think the problem is in your Restore config scripts.

That's not a new issue unfortunately.

[cadbomb]

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!

[bugacha]

We are still continuing to validate the issue you mentioned, please stay tuned.

Whats the latest on the fix please ?