[PROBLEM] Video Stutter

[nertskull]

(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?

I don't think I'm running it. I never set it up. So unless its on by default, I am not

This is the exports

Code:

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#
/media/Aspartic_Acid 10.23.24.0/24(rw,sync,no_subtree_check)

---

So I'm optimistic. It may be fixed.

I just set up nfs4 in the fstab. And I have restarted now 12 times and it mounts correctly every time and plays just great.

I've never had a streak that long before. So I'm thinking it may be fixed by telling it to be nfs4.

Does this seem plausible? Should I just test a few more times like this? Or should I be looking for something more?

As it is, I'm pretty excited, we may finally have things all working correctly.

---

(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.

I see. Well then maybe this means things are fixed by putting in nfs4