From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-raid@vger.kernel.org
Subject: LBS setup
Date: Sun, 24 May 2026 12:27:27 +0200 [thread overview]
Message-ID: <ahLSj1Ua5WJ0GTgY@lazy.lzy> (raw)
Hi all,
I've some questions about some recent
report from kernel.
I assume from 7.x.y, from what I understood.
Not sure about the <= 6.18 reported.
In the boot log there is:
md0: echo current LBS to md/logical_block_size to prevent data loss issues from LBS changes.
Note: After setting, array will not be assembled in old kernels (<= 6.18)
I found the docs stating:
logical_block_size
... Write the value before starting array. ...
Now, should we really copy the value from:
/sys/class/block/md0/queue/logical_block_size
to:
/sys/class/block/md0/md/logical_block_size
???
Note, the first in my system is 512, the
second is 0.
Second, the docs says "before starting array".
In case this is due (copy the value), how to do
for a system array?
I mean, the array where the whole OS lies.
If needed, is there any way to do this automatically?
Using mdadm or something?
Thanks,
bye,
--
piergiorgio
reply other threads:[~2026-05-24 10:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ahLSj1Ua5WJ0GTgY@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@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