2014-04-29, 18:16
(2014-04-29, 15:10)jbrew Wrote: For me NAS media playback (with FTV) works better/faster with NFS mount compared to SMB. I had no issues on ATV2 with NFS but with FTV that did not work. Read worked after I added 'insecure' to export file in NAS. Write for Thumbnails did not work even after adding anonuid to NAS exports till I saw Diegomejia's post - http://forum.xbmc.org/showthread.php?tid...pid1690670 , and it worked after a update (I did not do reinstall).
Here is a recap of what I did to make NFS (for linux based NAS) work for FTV. I believe these changes on NFS mount is Android related and not specific to FTV.
In this example - 192.168.1.101 is the ip address of FTV and 192.168.1.102 is the NAS.
In advancedsettings.xml for Thumbnail cache (write to NAS) add this in substitute.
Quote:<to>nfs://192.168.1.102/mnt/path_write/FTV/userdata_spmc/Thumbnails/</to>If you have multiple xbmc installation in FTV, use different folders for Thumbnails in those xmls.
Note I tried with userid and password here in path initially. That works in ATV2 (without insecure in NAS exports file) but does not work in FTV. To circumvent I had to update my exports file in NAS and add anonuid/anongid.
sources.xml remained same as what I had in ATV2. As mentioned above it worked after adding insecure in NAS exports file.
Quote:nfs://192.168.1.102/mnt/path_readAssuming you have a linux based NAS with a directory where you have provided read access and another directory with write access.
Edit your exports file (/ffp/etc/exports) with any available editor (vi).
By default on my NAS I had this on exports file.
Quote:/mnt/path_write 192.168.1.0/24(rw,no_root_squash)I changed exports file to
/mnt/path_read 192.168.1.0/24(rw,no_root_squash)
Quote:/mnt/path_write 192.118.1.101(rw,all_squash,insecure,anonuid=501,anongid=502)For starters, you can get anonuid and anongid (group id) by using command like this in NAS command line (use telnet to get into NAS if you have access) and it will vary depending on your NAS set up.
/mnt/path_read 192.118.1.101(ro,all_squash,insecure,anonuid=501,anongid=502)
Quote:cat /etc/passwdReboot NAS to get the exports in effect. Clear cache, clear data in FTV for XBMC, and then use -r option in desktop to update xbmc installation for NFS write to work in FTV XBMC.
NFS is less of a resource hog which is why it performs better then SMB.
On my Synology i had to do something simliar.run cat /etc/exports than I changed insecure_locks to insecure
Before
/volume1/media *(rw,async,no_wdelay,insecure_locks,no_root_squash,sec=sys,anonuid=0,anongid=0)
After.
/volume1/media *(rw,async,no_wdelay,insecure,no_root_squash,sec=sys,anonuid=0,anongid=0)
I would be interested to find out how many people are using smb and suggest they try nfs. I've heard of this being a problem for rasberry pi users. I'll test smb when i get home and see how much of a difference it is using SPMC on the FTV.