From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: Linux OS killed fio process because fio invoked oom_killer References: <56F17326.3000908@kernel.dk> <61A20AC4-3F8E-4B1E-A2C9-81BE827B188F@kernel.dk> <56F3F481.6050508@kernel.dk> <56F44286.8000706@kernel.dk> From: Jens Axboe Message-ID: <56F554CA.7080205@kernel.dk> Date: Fri, 25 Mar 2016 09:10:02 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: flash yan Cc: Jeff Furlong , "fio@vger.kernel.org" List-ID: On 03/25/2016 09:03 AM, flash yan wrote: > I have tried your patch. It fixed the issue. But I don't understand > "So we just kept piling on buffers to verify, but we never did". > You mean that fio didn't run any verify job with verify_async enabled? Right, it did not for your case. But that's because of the super short loop and the time_based setup, otherwise it would have. That was apparent while it was running too (not reads or V status), and in the final output (no reads there either). So it was a corner case where verify did not happen, since the referenced commit that broke it for that case. -- Jens Axboe