> -----Original Message----- > From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- > ow...@vger.kernel.org] On Behalf Of Elliott, Robert (Server Storage) > > I added some prints in aio_setup_ring and ioctx_alloc and > rebooted. This time it took much longer to hit the problem. It > survived dozens of ^Cs. Running a few minutes, though, IOPS > eventually dropped. So, sometimes it happens immediately, > sometimes it takes time to develop. > > I will rerun bisect-1 -2 and -3 for longer times to increase > confidence that they didn't just appear good.
Allowing longer run times before declaring success, the problem does appear in all of the bisect trees. I just let fio continue to run for many minutes - no ^Cs necessary. no-rebase: good for > 45 minutes (I will leave that running for 8 more hours) bisect-1: bad bisect-2: bad bisect-3: bad bisect-4: bad -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
