<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"></head><body style="font-family:Arial;font-size:14px"><p>
hi Peter,<br><br>
- as servers (masters and agents), I run now Debian "jessie" with Linux kernel 3.16.0-4<br>
- clients are the Windows(-7) client and a Ubuntu 14.04LTS native client<br><br>
I encounter the NFS-related problems with each of the clients.<br><br>
Meanwhile, I think that the alternative proposed by Roman (SSHFS) is worth a try !<br><br>
For the rest: TL is still a very nice product ! Might get some performance tuning documentation tough.<br><br>
brgds<br>
Rob<br><br>
Citeren Peter Astrand <<a href="mailto:astrand@cendio.se">astrand@cendio.se</a>>:</p>
<blockquote style="border-left:2px solid blue;margin-left:2px;padding-left:12px;" type="cite">
Hi and thanks for your feedback. We are aware of that these types of problems happens from time to time. The problem is actually not the use of the NFSv3 protocol, but the fact that we are using the standard Linux kernel NFS client, which is not well suited for this use case. This is also an area with constant development, so the behaviour (amount of problems) may depend on which kernel you use (ie affected by choice of distribution).<br><br>
Have you tried "tl-umount-localdrives -vas"? Does it help? It may take some time, but it should eventually succeed.<br><br>
Which Linux kernel & distribution are you running?<br><br>
For the future, we are considering change the server side to use a FUSE based NFS client, instead of the kernel client:<br><br><a href="https://www.cendio.com/bugzilla/show_bug.cgi?id=4900" target="_blank">https://www.cendio.com/bugzilla/show_bug.cgi?id=4900</a><br><br>
It could also be interesting to hear what kind of client platforms you are using.<br><br>
Best regards, Peter<br><br>
On Tue, 29 Nov 2016, Rob De Langhe wrote:<br><blockquote style="border-left:2px solid blue;margin-left:2px;padding-left:12px;" type="cite">
hi,<br><br>
I must say that the mechanism (up till TL-version 4.7) by which client-side media (hard disk, USB-stick, ...) are 'exported' via<br>
NFS to the TL-agents, is quite unstable.<br><br>
There is no bullet-proof procedure by which logout scripts can avoid that these NFS-mounts become 'stale'. Result is that the<br>
TL-agent can only recover from such 'stale' NFS mounts via a reboot. Or worse: if the TL-agent is a *NIX container then its 'guest'<br>
server (who runs the kernel) needs a reboot as well...<br><br>
-> is there no better mechanism to share the client-side media via the VNC client-to-agent tunnels? Another protocol than NFS is<br>
required to avoid the above problems.<br><br>
brgds<br>
Rob<br><br>
</blockquote>
---<br>
Peter Astrand ThinLinc Chief Developer<br>
Cendio AB <a href="https://cendio.com" target="_blank">https://cendio.com</a><br>
Teknikringen 8 <a href="https://twitter.com/ThinLinc" target="_blank">https://twitter.com/ThinLinc</a><br>
583 30 Linkoping <a href="https://facebook.com/ThinLincPhone" target="_blank">https://facebook.com/ThinLincPhone</a>: +46-13-214600 <a href="https://google.com/+CendioThinLinc" target="_blank">https://google.com/+CendioThinLinc</a></blockquote>
<br><br></body></html>