How can I get NFS to work correctly with NAS542 (nfs app bug workaround.)

deemon
deemon Posts: 9  Freshman Member
First Comment Friend Collector Third Anniversary
edited June 2019 in Personal Cloud Storage
Hi,
First I updated the NAS to latest firmware. V5.21(ABAG.2)
Then I enabled the NFS package. 1.3.0zypkg007
Then I added all 3 drives in NFS inside the GUI. When I look the exports file over telnet I see this:
/etc $ cat exports<br>/i-data/c65dd9d1/nfs *(rw,sync,crossmnt,fsid=0,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/c65dd9d1/nfs/toshiba 192.168.1.11(rw,sync,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/d2eb3296/nfs/wd-red 192.168.1.11(rw,sync,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/f9b5c33b/nfs/wd-red2 192.168.1.11(rw,sync,no_subtree_check,wdelay,no_root_squash) #<br>
now when I look for the shares in computer I see this:
$ showmount -e nas542.local<br>Export list for nas542.local:<br>/i-data/c65dd9d1/nfs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *<br>/i-data/f9b5c33b/nfs/wd-red2 192.168.1.11<br>/i-data/d2eb3296/nfs/wd-red&nbsp; 192.168.1.11<br>/i-data/c65dd9d1/nfs/toshiba 192.168.1.11<br>
However, when I mount the drives, the mounted directories are all empty. :-(

1. How can I make them actually show/access files?

2. Why is there invisible/unremovable in GUI /nfs * share already which I never created. Do I need it and if not, how to remove it (because it kind of looks like security risk to me)?

3. also in the GUI I see this for "wd-red":
NFSv3 Path: /i-data/d2eb3296/nfs/wd-red
NFSv4 Path: /wd-red
However it's inaccessible and inmountable with just "/wd-red" and I need to use "/i-data/d2eb3296/nfs/wd-red". Same thing for "/wd-red2". Why? But for the toshiba I can use /toshiba without any errors.



#NAS_Jun_2019

Accepted Solution

  • deemon
    deemon Posts: 9  Freshman Member
    First Comment Friend Collector Third Anniversary
    edited June 2019 Answer ✓
    Did some more telnet digging myself and what I found.
    in the NAS folders:
    /i-data/f9b5c33b/nfs/wd-red2<br>/i-data/d2eb3296/nfs/wd-red<br>/i-data/c65dd9d1/nfs/toshiba
    are also actually empty and the REAL drives are still intact with files as:
    /i-data/f9b5c33b/wd-red2<br>/i-data/d2eb3296/wd-red<br>/i-data/c65dd9d1/toshiba
    and the nfs-server part to the "/nfs/" folders actually WORK because when I created a new file to this mounted folder "ntoshiba" in computer (/i-data/c65dd9d1/nfs/toshiba)it appeared also into the /i-data/c65dd9d1/nfs/toshiba folder in NAS (as the first and single file in this folder). But not into the /i-data/c65dd9d1/toshiba where all the other files are.

    So basically the Zyxel NAS542 NFS app is bugged and points to WRONG folders and/or doesn't link them to the right ones.

    So AS A WORKAROUND right now I ended up modifying my /etc/exports as this:
    #/i-data/c65dd9d1/nfs 192.168.1.11(rw,async,insecure,crossmnt,fsid=0,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/c65dd9d1/toshiba 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/d2eb3296/wd-red 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/f9b5c33b/wd-red2 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>
    ...and everything works now. No thanks to Zyxel though :/

All Replies

  • deemon
    deemon Posts: 9  Freshman Member
    First Comment Friend Collector Third Anniversary
    edited June 2019 Answer ✓
    Did some more telnet digging myself and what I found.
    in the NAS folders:
    /i-data/f9b5c33b/nfs/wd-red2<br>/i-data/d2eb3296/nfs/wd-red<br>/i-data/c65dd9d1/nfs/toshiba
    are also actually empty and the REAL drives are still intact with files as:
    /i-data/f9b5c33b/wd-red2<br>/i-data/d2eb3296/wd-red<br>/i-data/c65dd9d1/toshiba
    and the nfs-server part to the "/nfs/" folders actually WORK because when I created a new file to this mounted folder "ntoshiba" in computer (/i-data/c65dd9d1/nfs/toshiba)it appeared also into the /i-data/c65dd9d1/nfs/toshiba folder in NAS (as the first and single file in this folder). But not into the /i-data/c65dd9d1/toshiba where all the other files are.

    So basically the Zyxel NAS542 NFS app is bugged and points to WRONG folders and/or doesn't link them to the right ones.

    So AS A WORKAROUND right now I ended up modifying my /etc/exports as this:
    #/i-data/c65dd9d1/nfs 192.168.1.11(rw,async,insecure,crossmnt,fsid=0,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/c65dd9d1/toshiba 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/d2eb3296/wd-red 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>/i-data/f9b5c33b/wd-red2 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,no_root_squash) #<br>
    ...and everything works now. No thanks to Zyxel though :/

  • deemon
    deemon Posts: 9  Freshman Member
    First Comment Friend Collector Third Anniversary
    And OH EFF how fast nfs is compared to default SAMBA share on zyxel. copying one file over SMB went with like 53MiB/s max; another same size 2GB file from the same folder over NFS came with 109MiB/s. Over TWICE as fast!
  • Mijzelf
    Mijzelf Posts: 2,816  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    <quote>in the NAS folders:
    /i-data/f9b5c33b/nfs/wd-red2<br>/i-data/d2eb3296/nfs/wd-red<br>/i-data/c65dd9d1/nfs/toshiba
    are also actually empty and the REAL drives are still intact with files as:
    /i-data/f9b5c33b/wd-red2<br>/i-data/d2eb3296/wd-red<br>/i-data/c65dd9d1/toshiba
    </quote>
    That is by design. On a ZyXEL NAS Samba and NFS shares cannot be mixed. I think that is done to prevent permission problems, as the Samba- and NFS users use incompatible ACL's.

    Using your modification of /etc/exports NFS will work fine, but be prepared to face some problems if you also use Samba.

  • deemon
    deemon Posts: 9  Freshman Member
    First Comment Friend Collector Third Anniversary
    edited June 2019
    That is by design. On a ZyXEL NAS Samba and NFS shares cannot be mixed. I think that is done to prevent permission problems, as the Samba- and NFS users use incompatible ACL's. Using your modification of /etc/exports NFS will work fine, but be prepared to face some problems if you also use Samba.

    Then that is just BAD design. The entire point of NAS is to share files between different computers and work as a kind of hub. If different systems and computers can't see each other files, then what's the point?

    also fixed! :blush: 

    /i-data/c65dd9d1/toshiba 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,all_squash,anonuid=501,anongid=500) #<br>/i-data/d2eb3296/wd-red 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,all_squash,anonuid=501,anongid=500) #<br>/i-data/f9b5c33b/wd-red2 192.168.1.11(rw,async,insecure,no_subtree_check,wdelay,all_squash,anonuid=501,anongid=500) #<br>



Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）