Re: possible regression fs corruption on 64GB nvme

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Robert Beckett <bob.beckett@xxxxxxxxxxxxx>
Subject: Re: possible regression fs corruption on 64GB nvme
From: Keith Busch <kbusch@xxxxxxxxxx>
Date: Mon, 9 Sep 2024 14:31:41 -0600
Cc: linux-nvme <linux-nvme@xxxxxxxxxxxxxxxxxxx>, Jens Axboe <axboe@xxxxxx>, Christoph Hellwig <hch@xxxxxx>, Sagi Grimberg <sagi@xxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, linux-mm <linux-mm@xxxxxxxxx>
In-reply-to: <Zt9amhUGs9FT5i-O@kbusch-mbp>
References: <191d810a4e3.fcc6066c765804.973611676137075390@collabora.com> <Zt9amhUGs9FT5i-O@kbusch-mbp>

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".

References:
- possible regression fs corruption on 64GB nvme
  - From: Robert Beckett
- Re: possible regression fs corruption on 64GB nvme
  - From: Keith Busch

Prev by Date: Re: [PATCH] mm: z3fold: deprecated ZSWAP_ZPOOL_DEFAULT_Z3FOLD as well
Next by Date: Re: [PATCH] mm: z3fold: deprecated ZSWAP_ZPOOL_DEFAULT_Z3FOLD as well
Previous by thread: Re: possible regression fs corruption on 64GB nvme
Next by thread: Re: possible regression fs corruption on 64GB nvme
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux