linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robert Beckett <bob.beckett@collabora.com>
To: "Keith Busch" <kbusch@kernel.org>
Cc: "linux-nvme" <linux-nvme@lists.infradead.org>,
	"Jens Axboe" <axboe@fb.com>, "Christoph Hellwig" <hch@lst.de>,
	"Sagi Grimberg" <sagi@grimberg.me>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"linux-mm" <linux-mm@kvack.org>
Subject: Re: possible regression fs corruption on 64GB nvme
Date: Tue, 10 Sep 2024 10:30:18 +0100	[thread overview]
Message-ID: <191db450152.e0b28690987786.6989198174827147639@collabora.com> (raw)
In-Reply-To: <Zt9bLa4TJT6L75aG@kbusch-mbp>






 ---- On Mon, 09 Sep 2024 21:31:41 +0100  Keith Busch  wrote --- 
 > On Mon, Sep 09, 2024 at 02:29:14PM -0600, Keith Busch wrote:
 > > As a test, could you try kernel parameter "nvme.io_queue_depth_set=2"?
 > 
 > Err, I mean "nvme.io_queue_depth=2".
 > 

Thanks, I'll give it a try along with your other questions and report back.

For clarity, the repro steps dropped a step. They should have included the make command:


$ dd if=/dev/urandom of=test_file bs=1M count=10240
$ desync make test_file.caibx test_file
$ sudo bash -c "echo 3 > /proc/sys/vm/drop_caches"
$ desync verify-index test_file.caibx test_file




  reply	other threads:[~2024-09-10  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 18:34 Robert Beckett
2024-09-09 19:29 ` Keith Busch
2024-09-09 20:29 ` Keith Busch
2024-09-09 20:31   ` Keith Busch
2024-09-10  9:30     ` Robert Beckett [this message]
2024-09-10 17:27       ` Robert Beckett
2024-09-10 17:53         ` Keith Busch
2024-09-11 16:56           ` Robert Beckett
2024-09-11 16:57             ` Robert Beckett
2024-09-11 17:08             ` Keith Busch
2024-09-11 17:17               ` Robert Beckett
2024-09-10  4:24 ` Christoph Hellwig
2024-09-10  9:37   ` Robert Beckett

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=191db450152.e0b28690987786.6989198174827147639@collabora.com \
    --to=bob.beckett@collabora.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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