If you are using fstab or autofs mounts, you could stress test the NAS to really see for sure of it’s NAS throughput or something with TVH. dd is your friend
this will create a 5GB file with random content. While that is running, open another ssh session and run the dd command again (with a different output filename)
Your fstab and TVH settings look OK to me. It’s strange that there is so much CPU load on the NAS while copying files. I wonder if you have a failing drive that’s causing lots of re-writes.
I assume that the drive is internal to the NAS. Does the NAS have USB ports so you could test another drive?
Just added the S.M.A.R.T status
Nothing really sticks as far as I’m concerned…
But heck - I don’t have a whole lot of faith when it comes to the S.M.A.R.T feature…
Sorry – I thought you were currently running tvh and storage on the NAS, with plans to move TVH over to the Vero.
It seems like something isn’t quite right on the NAS. Live TV isn’t tremendously intensive in terms of throughput. A NAS should be able to keep up with this.
Adding the streaming rates - and converting to MB/s would be around 5,7 (please correct me if I’m wrong).
During my tests - monitoring the NAS.
Again and again - I see a process - bdflush turn up - consuming 80-90% of the CPU.
(I know it’s only consuming 0.63% in my earlier screendumps - but very often it spikes)
Not an expert when it comes to Linux - but could that be the problem? Or is it just normal Linux logics?
I will definitely give the NAS a factory reset - and setup the NFS share again. Just because I’m curious