<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 25 May 2017 at 11:22, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vdsm and ovirt-imageio use /var/tmp because we need file system supporting direct I/O. /tmp is using tmpfs which does not support it. <div><br></div><div>We have no need for "cached" data kept after a test run, and we cannot promise that test will never leave junk in /var/tmp since tests run before they are reviewed. Even correct tests can leave junk if the test runner is killed (for example, on timeout).</div><div><br></div><div>The only way to keep slaves clean is to clean /tmp and /var/tmp after each run. Treating /var/tmp as cache is very wrong.</div></blockquote><div><br></div><div>You need to differentiate between the '/var/tmp' you see from your<br>scripts to the one we are talking about here.<br><br></div><div>- When you use /var/tmp in your script you use the one inside the mock<br> environment. It is specific to yore script run time environment and <br> will always be wiped out when its done.<br><br></div><div>- We are talking about "/var/tmp" _of_the_execution_slave_, the only<br> way you can get to it is either specifically bind-mount it from the <br></div><div> "*.mounts" file, or have some daemon like libvirtd or dockerd write<br></div><div> to it.<br></div></div><br></div><div class="gmail_extra">BTW if you want any guarantees about the FS you are using, you better <br>bind-mount something to the point you are writing to, otherwise things <br>will break when we make infrastructure changes like for example moving <br></div><div class="gmail_extra">the chroots to RAM or onto layered file-systems.<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Barak Korren<br>RHV DevOps team , RHCE, RHCi<br>Red Hat EMEA<br><a href="http://redhat.com" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" target="_blank">redhat.com/trusted</a></div>
</div></div>