Linux block layer
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Salman Qazi <sqazi@google.com>,
	Jesse Barnes <jsbarnes@google.com>,
	Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH V2] block: Prevent hung_check firing during long sync IO
Date: Wed, 18 Mar 2020 19:07:11 +0800	[thread overview]
Message-ID: <20200318110711.GA1920@ming.t460p> (raw)
In-Reply-To: <3f8eb43f-4ad7-11f1-380c-c11969fe19ad@cloud.ionos.com>

On Wed, Mar 18, 2020 at 11:55:09AM +0100, Guoqing Jiang wrote:
> Hi Ming,
> 
> On 3/18/20 4:43 AM, Ming Lei wrote:
> > submit_bio_wait() can be called from ioctl(BLKSECDISCARD), which
> > may take long time to complete, as Salman mentioned, 4K BLKSECDISCARD
> > takes up to 100 second on some devices. Also any block I/O operation
> > that occurs after the BLKSECDISCARD is submitted will also potentially
> > be affected by the hung task timeouts.
> > 
> > Another report is that task hang can be observed when running mkfs
> > over raid10 which takes a small max discard sectors limit because
> > of chunk size.
> 
> Could you point the link about the raid10 task hang? And we have observed
> task hang with raid5, not sure it is related or not.
> 
> Our set up is md/raid5 -> 100+ LVs (fs is created on top of one LV), run heavy
> IOs on LVs and dbench on the LV with fs, then dbench hangs with 'D' state.

Red Hat Bugzilla 1813383.


Thanks,
Ming


  reply	other threads:[~2020-03-18 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  3:43 [PATCH V2] block: Prevent hung_check firing during long sync IO Ming Lei
2020-03-18 10:55 ` Guoqing Jiang
2020-03-18 11:07   ` Ming Lei [this message]
2020-03-18 14:48 ` Jens Axboe

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=20200318110711.GA1920@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=guoqing.jiang@cloud.ionos.com \
    --cc=jsbarnes@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=sqazi@google.com \
    /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