mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linan666@huaweicloud.com
Cc: <song@kernel.org>, <yukuai3@huawei.com>,
	<linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<martin.petersen@oracle.com>, <bvanassche@acm.org>,
	<hch@infradead.org>, <filipe.c.maia@gmail.com>,
	<yangerkun@huawei.com>, <yi.zhang@huawei.com>
Subject: Re: [PATCH v3 2/2] md: allow configuring logical_block_size
Date: Mon, 25 Aug 2025 15:51:44 -0400	[thread overview]
Message-ID: <yq15xebqiwu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250825075924.2696723-3-linan666@huaweicloud.com> (linan's message of "Mon, 25 Aug 2025 15:59:24 +0800")


> Previously, raid array used the maximum logical_block_size (LBS) of
> all member disks. Adding a larger LBS during disk at runtime could
> unexpectedly increase RAID's LBS, risking corruption of existing
> partitions. Simply restricting larger-LBS disks is inflexible. In some
> scenarios, only disks with 512 LBS are available currently, but later,
> disks with 4k LBS may be added to the array.

Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>

-- 
Martin K. Petersen

  reply	other threads:[~2025-08-25 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25  7:59 [PATCH v3 0/2] make logical_block_size configurable linan666
2025-08-25  7:59 ` [PATCH v3 1/2] md: prevent adding disks with larger logical_block_size to active arrays linan666
2025-08-25  8:10   ` Paul Menzel
2025-08-25  8:43     ` Li Nan
2025-08-27  9:29   ` Yu Kuai
2025-08-25  7:59 ` [PATCH v3 2/2] md: allow configuring logical_block_size linan666
2025-08-25 19:51   ` Martin K. Petersen [this message]
2025-08-27  9:39   ` Yu Kuai

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=yq15xebqiwu.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=bvanassche@acm.org \
    --cc=filipe.c.maia@gmail.com \
    --cc=hch@infradead.org \
    --cc=linan666@huaweicloud.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.com \
    /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

all inboxes | Powered by JetHome®