From: Coly Li <colyli@suse.de>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: "Kai Krakow" <kai@kaishome.de>,
linux-bcache@vger.kernel.org,
"Frédéric Dumas" <f.dumas@ellis.siteparc.fr>,
"Kent Overstreet" <kent.overstreet@gmail.com>
Subject: Re: Consistent failure of bcache upgrading from 5.10 to 5.15.2
Date: Mon, 7 Feb 2022 14:11:48 +0800 [thread overview]
Message-ID: <c9ebe2b9-d896-4f6e-ecf9-504bd98abe76@suse.de> (raw)
In-Reply-To: <8799ba1c-5c12-d69b-948f-4df9667a801a@suse.de>
On 1/6/22 11:49 PM, Coly Li wrote:
> On 1/6/22 10:51 AM, Eric Wheeler wrote:
>
>>
>> I'm not sure how to format it 4k, but this is how Frédéric set it to 512
>> bytes and fixed his issue:
>>
>> # intelmas start -intelssd 0 -nvmeformat LBAFormat=0
>> # intelmas start -intelssd 1 -nvmeformat LBAFormat=0
>
> Copied. Let me try to find Intel P3700 firstly.
Thanks to Lenovo, they lent me P3700 PCIe SSD for bcache testing and
debug. Now I format the card to 4K sector size and see the new 4k sector
size from fdisk output.
I start to run fio with 8 io jobs and 256 io depth, 4K random write. Let
me see what may happen. If any one has advice to reproduce the
non-aligned I/O error more easily, please hint me.
Coly Li
next prev parent reply other threads:[~2022-02-07 6:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 10:10 Consistent failure of bcache upgrading from 5.10 to 5.15.2 Kai Krakow
2021-11-16 11:02 ` Coly Li
2021-11-18 10:27 ` Kai Krakow
2021-11-20 0:06 ` Eric Wheeler
2021-11-23 8:54 ` Coly Li
2021-11-23 9:30 ` Kai Krakow
2022-01-06 15:32 ` Coly Li
2022-01-06 2:51 ` Eric Wheeler
2022-01-06 9:25 ` Frédéric Dumas
2022-01-06 15:55 ` Coly Li
2022-01-08 6:57 ` Coly Li
2022-01-06 15:49 ` Coly Li
2022-02-07 6:11 ` Coly Li [this message]
2022-02-07 7:37 ` Coly Li
2022-02-07 8:10 ` Kai Krakow
2022-02-07 8:13 ` Coly Li
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=c9ebe2b9-d896-4f6e-ecf9-504bd98abe76@suse.de \
--to=colyli@suse.de \
--cc=bcache@lists.ewheeler.net \
--cc=f.dumas@ellis.siteparc.fr \
--cc=kai@kaishome.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@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).