On Mon, Mar 5, 2018 at 12:45 AM, Ruvinsky, Konstantin <Konstantin.Ruvinsky@xxxxxxxx> wrote: > Hi, > > Do you see the same behavior for stonewalled size-based write-only and read-verify jobs? I'm not using verify, so no idea re your question. That's the config in question, with some (irrelevant) omissions. [global] thread=1 group_reporting=1 direct=1 verify=0 ramp_time=0 [precond] numjobs=1 iodepth=128 rw=write bs=128k size=4g [randrw] stonewall numjobs=4 iodepth=32 rw=randrw bs=4k runtime=1m Regards, Andrey > > Regards > Konstantin > > -----Original Message----- > From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Andrey Kuzmin > Sent: Sunday, March 4, 2018 11:36 PM > To: fio@xxxxxxxxxxxxxxx > Subject: Size and time-based jobs under the same config file > > I see a run of the subj resulting in the second, time-based job (which is stonewalled to start after the size-based one) ending prematurely, with its lifetime apparently consumed by the size-based job. This used to work just a couple of years back ;). Am I missing something? > > Regards, > Andrey > -- > To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
