From: Coly Li <colyli@suse.de>
To: "Frédéric Dumas" <f.dumas@ellis.siteparc.fr>
Cc: Eric Wheeler <bcache@lists.ewheeler.net>,
Kai Krakow <kai@kaishome.de>,
linux-bcache@vger.kernel.org,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: Consistent failure of bcache upgrading from 5.10 to 5.15.2
Date: Thu, 6 Jan 2022 23:55:37 +0800 [thread overview]
Message-ID: <0eb291b1-86af-94ed-b765-9b632050ed9f@suse.de> (raw)
In-Reply-To: <7212111D-5181-458B-B774-006D3B08A9AE@ellis.siteparc.fr>
On 1/6/22 5:25 PM, Frédéric Dumas wrote:
> Hello!
>
> Many thanks to Eric for describing here and in his previous email the bug I experienced using bcache on SSDs formatted as 4k sectors. Thanks also to him for explaining to me that all I had to do was reformat the SSDs into 512-byte sectors to easily get around the bug.
>
>
>> 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
>
> Right.
> To format an Intel NVMe P3700 back to 4k sectors, the command is as follows:
>
> # intelmas start -intelssd 0 -nvmeformat LBAFormat=3
>
>
>> The parameter LBAformat specifies the sector size to set. Valid options are in the range from index 0 to the number of supported LBA formats of the NVMe drive, however the only sector sizes supported in Intel® NVMe drives are 512B and 4096B which corresponds to indexes 0 and 3 respectively.
>
> Source: https://www.intel.com/content/www/us/en/support/articles/000057964/memory-and-storage.html
>
> Oddly enough the user manual for the intelmass application [1] (formerly isdct) forgets to specify the possible values to be given to the LBAformat argument, which makes it much less useful. :-)
Hi Frederic,
Many thanks for the information. BTW, could you please tell me the
detail information about your Intel NVMe P3700 SSD, I will try to find
it in local market.
Coly Li
next prev parent reply other threads:[~2022-01-06 15:55 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 [this message]
2022-01-08 6:57 ` Coly Li
2022-01-06 15:49 ` Coly Li
2022-02-07 6:11 ` Coly Li
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=0eb291b1-86af-94ed-b765-9b632050ed9f@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).