linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: oleksandr@natalenko.name
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, Shaohua Li <shli@kernel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram
Date: Wed, 30 Aug 2017 12:58:21 +0200	[thread overview]
Message-ID: <ae216831876b8b71ebc1590a44731db7@natalenko.name> (raw)
In-Reply-To: <20170830080628.GA2402@ming.t460p>

Hi.

So, current summary:

1) first patch + debug patch: I can reproduce the issue in wild, but not 
with pm_test set;
2) first patch + debug patch + second patch: I cannot reproduce issue at 
all, neither with "none", nor with "mq-deadline".

Thus, "blk-mq: align to legacy path for implementing blk_execute_rq" + 
"blk-mq: add requests in the tail of hctx->dispatch" look like a proper 
fix. Thanks for that!

> I setup dm-crypt on /dev/md0 directly, could you show me how to setup 
> lvm on raid10?

If still relevant, here is a layout:

===
sda                 8:0    0    8G  0 disk
|-sda1              8:1    0  128M  0 part   /boot/EFI
`-sda2              8:2    0  7.9G  0 part
   `-md0             9:0    0  7.9G  0 raid10
     `-system-root 253:0    0  7.9G  0 lvm    /
sdb                 8:16   0    8G  0 disk
|-sdb1              8:17   0  128M  0 part
`-sdb2              8:18   0  7.9G  0 part
   `-md0             9:0    0  7.9G  0 raid10
     `-system-root 253:0    0  7.9G  0 lvm    /
===

Anything else you'd like /me to test?

30.08.2017 10:06, Ming Lei написав:
> …SNIP…
> Please try the following patch and previous patch together and see
> if they make a difference:
> …SNIP…

  reply	other threads:[~2017-08-30 10:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 11:45 I/O hangs after resuming from suspend-to-ram Oleksandr Natalenko
2017-08-26 10:37 ` Oleksandr Natalenko
2017-08-26 10:48   ` Oleksandr Natalenko
2017-08-26 11:19     ` Martin Steigerwald
2017-08-26 17:17       ` Wols Lists
2017-08-26 19:33         ` Martin Steigerwald
2017-08-26 13:32     ` Oleksandr Natalenko
2017-08-27  6:02     ` Ming Lei
2017-08-27  7:43       ` Oleksandr Natalenko
2017-08-28 12:58         ` Ming Lei
2017-08-28 13:10           ` Martin Steigerwald
2017-08-28 13:32             ` Ming Lei
2017-09-20 17:25               ` Martin Steigerwald
2017-09-20 22:17                 ` Ming Lei
2017-09-24 17:33                   ` Martin Steigerwald
2017-09-25  2:59                     ` Ming Lei
2017-09-25 14:13                       ` Martin Steigerwald
2017-09-20 22:20             ` Ming Lei
2017-09-21  7:30               ` Martin Steigerwald
2017-09-21  7:33                 ` Martin Steigerwald
2017-08-28 18:22           ` Oleksandr Natalenko
2017-08-29  0:24             ` Ming Lei
2017-08-29 15:52               ` Oleksandr Natalenko
2017-08-30  2:15                 ` Ming Lei
2017-08-30  5:17                   ` Ming Lei
2017-08-30  6:15                     ` oleksandr
2017-08-30  8:06                       ` Ming Lei
2017-08-30 10:58                         ` oleksandr [this message]
2017-08-30 14:37                           ` Ming Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ae216831876b8b71ebc1590a44731db7@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=shli@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).