Hi Sirk,<div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If you want some practical information on ploop: We are using it in a<br>
highly productive environment.<br>
It was either, try ploop and hope it works, or have the systems fail<br>
every 2nd day.<br>
So we decided to use ploop and are more than happy.<br>
It even solves a lot of issues we had with the private areas directly<br>
on the nfs share.<br>
But of course, thats totally up to you.<br>
I started with only a few "unimportant" CTs and then merged everything<br>
after a while (42 CTs).<br>
</blockquote><div><br></div><div>Thanks for the info, much appreciated!</div><div><br></div><div>Maybe a little off topic, but I am curious to know: At the moment I find it very convenient to go directly into a containers filesystem from the hardware node - i.e. something like /vz/private/xxx/var/log/... etc - Would I be correct in presuming that by using ploop this will no longer be possible? I know I could just setup a test system and try it out but if you know already it would save me some time ;) </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So you have a different FileSystem for the "problem"-Container that is<br>
even on a different disk ?<br>
If that is the case, this CT should not affect the others at all in terms of IO.<br><br></blockquote><div><br></div><div>Indeed, this is the only container on that filesystem and that physical drive. This time there were no "spill over" but previous times when load hit 50 or more the load certainly did spill into other containers.</div>
<div> </div><div>Best,</div><div>Rene</div><div> </div></div></div>