On 4/10/18 8:30 PM, Ming Lei wrote:
> On Tue, Apr 10, 2018 at 08:08:43PM -0600, Jens Axboe wrote:
>> On 4/10/18 8:02 PM, Ming Lei wrote:
>>> On Tue, Apr 10, 2018 at 09:51:41AM -0600, Jens Axboe wrote:
Hi Ming,
Ran the above blktests on the current tree, and we end up getting
a h
On Tue, Apr 10, 2018 at 08:08:43PM -0600, Jens Axboe wrote:
> On 4/10/18 8:02 PM, Ming Lei wrote:
> > On Tue, Apr 10, 2018 at 09:51:41AM -0600, Jens Axboe wrote:
> >> Hi Ming,
> >>
> >> Ran the above blktests on the current tree, and we end up getting
> >> a hang that we never recover from. There's
On 4/10/18 8:02 PM, Ming Lei wrote:
> On Tue, Apr 10, 2018 at 09:51:41AM -0600, Jens Axboe wrote:
>> Hi Ming,
>>
>> Ran the above blktests on the current tree, and we end up getting
>> a hang that we never recover from. There's on request perpetually
>> stuck:
>>
>> root@dell:/sys/kernel/debug/bloc
On Tue, Apr 10, 2018 at 09:51:41AM -0600, Jens Axboe wrote:
> Hi Ming,
>
> Ran the above blktests on the current tree, and we end up getting
> a hang that we never recover from. There's on request perpetually
> stuck:
>
> root@dell:/sys/kernel/debug/block/nvme0n1/hctx2# cat busy
> 5e2b09
Hi Ming,
Ran the above blktests on the current tree, and we end up getting
a hang that we never recover from. There's on request perpetually
stuck:
root@dell:/sys/kernel/debug/block/nvme0n1/hctx2# cat busy
5e2b09fe {.op=READ, .cmd_flags=, .rq_flags=DONTPREP|IO_STAT|STATS,
.state=in_flig
