<div dir="ltr">Thanks Pavel!<div><br></div><div>Looks like rlimit restore fails: </div><div>if (r->rlim_cur > r->rlim_max) fails because r->rlim_max is 0</div><div><br></div><div>What could be wrong?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 23, 2015 at 4:59 AM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 07/23/2015 03:21 AM, CRIU criu wrote:<br>
> Hi,<br>
><br>
> I'm facing an issue with open()ing a file after a successful restore. It<br>
> fails with "Too many open files" error. I've tested with a LD_PRELOAD wrapper<br>
> library overriding open()/close() lib calls to verify that the process doesn't<br>
> open too many files and that there is no FD leakage.<br>
<br>
</span>Do you play with android binder device? Quick kernel grep shows that<br>
it reports EMFILE from some of its operation(s).<br>
<span class=""><br>
> As long as the app runs before cr-dump, open() works fine, but fails once<br>
> restored. Is anybody else facing this problem? What file should I start<br>
> looking in order to fix this? Thanks!<br>
<br>
</span>Do you restore on the same node, or on another? The issue may be either<br>
in rlimits restore or in different sysctl fs.nr_open value.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Pavel<br>
</font></span></blockquote></div><br></div>