linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jaco Kroon <jaco@uls.co.za>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: LVM kernel lockup scenario during lvcreate
Date: Wed, 12 Jul 2023 06:43:19 -0700	[thread overview]
Message-ID: <1cf96e3b-e5e0-bcdb-df2b-ef9cbe51f9ca@acm.org> (raw)
In-Reply-To: <ea29d76f-99c0-fcf2-09a3-4cc2e18f87da@uls.co.za>

On 7/12/23 03:12, Jaco Kroon wrote:
> Ideas/Suggestions?

How about manually increasing the workload, e.g. by using fio to 
randomly read 4 KiB fragments with a high queue depth?

Bart.


  reply	other threads:[~2023-07-12 13:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  7:29 LVM kernel lockup scenario during lvcreate Jaco Kroon
2023-06-12 18:40 ` Bart Van Assche
2023-06-12 19:36   ` Jaco Kroon
2023-06-18 23:28     ` Bart Van Assche
2023-06-18 19:34   ` Jaco Kroon
2023-06-18 23:56     ` Bart Van Assche
2023-06-19  6:06       ` Jaco Kroon
2023-06-26  8:30       ` Jaco Kroon
2023-06-26 16:42         ` Bart Van Assche
2023-06-26 23:29           ` Jaco Kroon
2023-07-11 13:22             ` Jaco Kroon
2023-07-11 14:45               ` Bart Van Assche
2023-07-12 10:12                 ` Jaco Kroon
2023-07-12 13:43                   ` Bart Van Assche [this message]
     [not found]                     ` <ef2812b4-7853-9dda-85dd-210636840a59@uls.co.za>
2023-08-24  7:29                       ` Jaco Kroon
2023-08-24 17:13                         ` Bart Van Assche
2023-08-24 20:16                           ` Jaco Kroon
2023-08-24 17:29   ` Laurence Oberman
2023-08-24 20:01     ` Jaco Kroon
2023-08-24 20:19       ` Laurence Oberman
2023-08-24 23:40         ` Jaco Kroon
2023-08-25 12:01           ` Laurence Oberman
2023-08-26 18:18             ` Jaco Kroon
2023-09-06 21:03             ` Jaco Kroon
2023-09-06 21:22               ` Jens Axboe
2023-09-06 22:05                 ` Jaco Kroon

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=1cf96e3b-e5e0-bcdb-df2b-ef9cbe51f9ca@acm.org \
    --to=bvanassche@acm.org \
    --cc=jaco@uls.co.za \
    --cc=linux-block@vger.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).