Re: Windows: FIO randomly hangs using attached script

[Rob Scheepens <rob.scheepens@nutanix.com>]

Merging since Rebecca's reply lost the thread:


From memory, my runs would also get somewhere over #100, but I'll confirm next week.

\Rob


On 03/07/2018 09:01 AM, Sitsofe Wheeler wrote:
Thanks for following up.

Do you happen to know how far it would get on runs where it went on to
hang? Would it be it in the middle of a job or was it still doing
setup or varied? Would it take hours to happen?

I saw hangs at job 130 and 134.

--
Rebecca

On 07/03/2018, 18:01, "Sitsofe Wheeler" <sitsofe@gmail.com> wrote:

    Thanks for following up.
    
    Do you happen to know how far it would get on runs where it went on to
    hang? Would it be it in the middle of a job or was it still doing
    setup or varied? Would it take hours to happen?
    
    On 7 March 2018 at 15:39, Rob Scheepens <rob.scheepens@nutanix.com> wrote:
    > Adding to David's comments: my success percentage was roughly 30%. Most of the time, 2 out of 3 runs would hang.
    >
    > Thanks for your involvement here Sitsofe.
    >
    > \Rob
    >
    >
    > On 07/03/2018, 17:33, "David Knierim" <knierim@nutanix.com> wrote:
    >
    >     Sitsofe,
    >        Thanks for your interest in resolving this issue.  I no longer have a system to dig into this issue at the moment, but I will attempt to get back to this issue soon.
    >       That being said, I like your questions and I am happy to answer them:
    >
    >     >  can you check whether fio 3.5 also reproduces the problem?
    >     When I get a system to run on, I will attempt to reproduce the issue with fio 3.5.
    >
    >     Yes, the example fio command line examples you showed are indeed what the script is supposed to be doing.
    >
    >     If it helps, I also have a bash script which generates the same fio commands as the python script which also reproduces the issue.
    >
    >     I have not attempted to reproduce the issue with files or less raw disks.   I can see your desire for a simplified reproducer.   When I get back to this issue, I will see what I can come up with.   I am sure something simpler will reproduce the issue, but I have not spent the time to find something simpler that works.  I will explore number of disks/files, numjobs and also determine if the working set makes any difference.
    >
    >     In my experience, the python script never completed when run on Windows.  Rob had better luck than I did and the script ran to completion for him several times, but it also showed the failure multiple times as well, but I don't remember what the pass percentage was for him.
    >
    >     When I run the same python or bash script on Linux (just updating the path to the raw disks and the ioengine), it runs 100% reliably.
    
    -- 
    Sitsofe | https://urldefense.proofpoint.com/v2/url?u=http-3A__sucs.org_-7Esits_&d=DwIFaQ&c=s883GpUCOChKOHiocYtGcg&r=OMged-t_5I_fmfpUaT3vaA06lgLL_alYnDQJxHmXz64&m=927s0SaucUQFFVqXcunP1_PBnr0xEHUL8d_bKt-VIUE&s=vD6ZYXWmBRWz5kR8R4WKQF7b3l4BmLfVYl_uHRZGKq0&e=