(4th Oct, 2013 04:40 AM)mk01 Wrote:  @nertskull

got the same shutters. then changed nfs mount options and used

Code:

vers=3,rsize=262144,wsize=65536

in any case the buffers change was for me enough to play the video with sw DTS decode without shutters. still I always get ONE at the very beginning (in first 5s) but then no single one until finish.

report back.

(4th Oct, 2013 09:29 PM)nertskull Wrote:  The problem is, now when I ask a video to play, sometimes nothing happens. So I try again. And nothing happens. And then a error pops up saying that an error occurred and the video couldn't be played.

So I restart the Pi and sometimes it works, sometimes it doesn't. But when it works, all videos play and everything is smoother now. But sometimes I have to restart 3 or 4 times.

(4th Oct, 2013 11:30 PM)mk01 Wrote:  and the NFS is mounted successfully each time (according to mount)? we spend much time on this, so maybe few more experiments with changing the buffers to be the same size for rsize and wsize could not harm.

so for instance put it both to 262144 or 65536 or even remove the two parameters completely (reverting to your previous options).

I could not find an output of "mount" without the changes to fstab so I don't even know what version of NFS was used (2/3), udp or tcp transport etc. It would be nice to see it for me. then maybe I get another ideas
.

(5th Oct, 2013 08:05 AM)nertskull Wrote:  This is my fstab line. Is something wrong with it? Or is it an issue elsewhere?

Code:

10.23.24.137:/media/Aspartic_Acid /mnt/Aspartic_Acid nfs _netdev,defaults,user,auto,noatime,intr 0 0

or

Code:

10.23.24.137:/media/Aspartic_Acid /mnt/Aspartic_Acid nfs _netdev,defaults,user,auto,noatime,intr,rsize=262144,wsize=65536 0 0

BOTH will give failures. But the 2nd, when it does work, prevents me from stuttering in playback.

(5th Oct, 2013 08:56 AM)mk01 Wrote:  please post output of "mount". I need to see what others parameters are. mount will output them.

(5th Oct, 2013 09:30 AM)nertskull Wrote:  

Code:

10.23.24.137:/media/Aspartic_Acid on /mnt/Aspartic_Acid type nfs4 (rw,nosuid,nodev,noexec,noatime,vers=4.0,rsize=262144,wsize=65536,namlen=255,har​d,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.23.24.122,local_loc​k=none,addr=10.23.24.137,_netdev)

(5th Oct, 2013 09:37 AM)mk01 Wrote:  

(5th Oct, 2013 09:30 AM)nertskull Wrote:  

Code:

10.23.24.137:/media/Aspartic_Acid on /mnt/Aspartic_Acid type nfs4 (rw,nosuid,nodev,noexec,noatime,vers=4.0,rsize=262144,wsize=65536,namlen=255,har​d,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.23.24.122,local_loc​k=none,addr=10.23.24.137,_netdev)

and this nfs4 mount with smaller buffers is lagging as well? what exactly is the server (brand / type) ?

(5th Oct, 2013 09:37 AM)mk01 Wrote:  yes, they are the same

what happens if you put it the right way for nfs4?

in fstab change fstype from nfs to nfs4 and to mount options add vers=4.

(5th Oct, 2013 09:46 AM)mk01 Wrote:  what is output of

Code:

rpcinfo -p 10.23.24.137

Quote:

Code:

and

showmount -e 10.23.24.137

?

(5th Oct, 2013 09:45 AM)nertskull Wrote:  The server is just a pc I built. It is got plenty of power. Its an amd phenom II with 8Gb of RAM and gigabit ethernet. Its running linux mint 64bit. I highly doubt my server is the issue. I've been streaming videos off of it to xbmc on other computers for a long time. But who knows, maybe it does need to be tweaked.

(5th Oct, 2013 09:46 AM)nertskull Wrote:  

Code:

xbian@xbian ~ $ sudo showmount -e 10.23.24.137
Export list for 10.23.24.137:
/media/Aspartic_Acid 10.23.24.0/24

I'm testing mounting as nfs4 still

(5th Oct, 2013 09:55 AM)mk01 Wrote:  

(5th Oct, 2013 09:45 AM)nertskull Wrote:  The server is just a pc I built. It is got plenty of power. Its an amd phenom II with 8Gb of RAM and gigabit ethernet. Its running linux mint 64bit. I highly doubt my server is the issue. I've been streaming videos off of it to xbmc on other computers for a long time. But who knows, maybe it does need to be tweaked.

I don't want to say it IS a problem, but I have exactly the same way build media storage (it is ubuntu 12.04), NFS3/4 allowed, usage pattern the same (nfs mounted from fstab - with just fstype nfs4 and specified wsize and rsize) and never have had such issues.
(I have second NFS provider on MacOSX server (nfs3 only) for home dirs exports and situation the same for any connects to it).

Even XBMC connect with no issues, shows the NFS in browser, you can add sources and play files directly with it.

Of course it doesn't mean if I don't have issues with the RPI setup there must be zero issues for others, but indeed it is quite suspicious - specially if the setup looks to be the "same". It's problem on one side or the other and I would like to find out.

---

(5th Oct, 2013 09:46 AM)nertskull Wrote:  

Code:

xbian@xbian ~ $ sudo showmount -e 10.23.24.137
Export list for 10.23.24.137:
/media/Aspartic_Acid 10.23.24.0/24

I'm testing mounting as nfs4 still

and for the info to be completed, can you also copy /etc/exports?

are you running idmapd on the server as well?

(5th Oct, 2013 09:55 AM)mk01 Wrote:  

---

@nertskull

just small note to using nfs4/nfs . nfs4 requires idmapd running on both sides (client / server). on xbian, idmapd gets automatically started if nfs4 is found in /etc/fstab or if is forced to start from /etc/default/nfs-common. that's why I was asking to try the correct nfs4 in fstab.