Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Wol <antlists@youngman.org.uk>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: LBS setup
Date: Sat, 11 Jul 2026 15:22:30 +0200	[thread overview]
Message-ID: <alJDltJ9tc6tJCcj@lazy.lzy> (raw)
In-Reply-To: <a2a4e6f6-5521-44f7-b045-7432e3e8e757@youngman.org.uk>

On Fri, Jul 10, 2026 at 09:43:56PM +0100, Wol wrote:
> On 10/07/2026 18:54, Piergiorgio Sartor wrote:
> > Hi Wol
> > 
> > thanks for the answer.
> > 
> > My question is about "what to do?".
> > Not much what happened.
> > 
> > The log says we should copy some size
> > from somewhere to somewhere else.
> > The docs says this should be done
> > with array at rest.
> > 
> > Is there any documentation about this?
> > Should we just ignore the log?
> > What should be done, if any?
> > 
> > The log:
> > 
> > md1: 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)
> 
> Ah. Personally I wouldn't do anything, then. Are you using any systems with
> kernel 6.18 or earlier?
> 
> Are you likely to use any kernels 6.18 or earlier in the future?
> 
> If the answer to both questions is no, then you're not going to have any
> trouble ...

Thanks again for the answer.

Nevertheless, sorry if I insist.
What I understand from the log message is
that if I do *not* copy the LBS I can get
data loss. If I do copy the LBS, I will
not be anymore backward compatible.

This backward compatibility does not seem
interesting for me, hence I should copy
this LBS.
Which then begs the question: how?

I mean, this seems the logical conclusion
from what I understood from the log.

Also, why to have this log in the first place?
The kernel is 7.1.3, so if everything would
be fine with it, no need to log anything.

I do not know...

Anyway, sorry again if I bother...

Thanks,

bye,

-- 

piergiorgio

      reply	other threads:[~2026-07-11 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24 10:27 LBS setup Piergiorgio Sartor
2026-07-10 16:20 ` Piergiorgio Sartor
2026-07-10 17:10   ` Wol
2026-07-10 17:54     ` Piergiorgio Sartor
2026-07-10 20:43       ` Wol
2026-07-11 13:22         ` Piergiorgio Sartor [this message]

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=alJDltJ9tc6tJCcj@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --cc=antlists@youngman.org.uk \
    --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