jplour

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by jplour

  1. Where did you dig? Was looking today to my browser history and can't find where. The fact is with disabling nfs3 READDIRPLUS resolves my issue. It was something related with kodi/xbmc nfs implementation on windows not supporting 64 inodes. Can't find the page I saw supporting it.
  2. I have a similar situation, but what I already figured out is that is working when I access from a linux machine (regular nfs mount), but not on kodi in windows. After some digging up, I managed to "fix" it with manual adding "nordirplus" on nfs export options: "/mnt/user/media" -async,no_subtree_check,fsid=100,nordirplus *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash) and issueing a exportfs -ra to reload the new setup. This doesn't stay permanent because get override with time, but didn't had time yet to figure out, why this works and how to permanent fix it. Giving here my finds to see if it helps out.