[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <c3124729-4b78-4c45-9b13-b74d59881dba@fnnas.com>
Date: Thu, 6 Nov 2025 21:30:37 +0800
From: "Yu Kuai" <yukuai@...as.com>
To: "Xiao Ni" <xni@...hat.com>
Cc: "Li Nan" <linan666@...weicloud.com>, <corbet@....net>, <song@...nel.org>,
<hare@...e.de>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-raid@...r.kernel.org>,
<yangerkun@...wei.com>, <yi.zhang@...wei.com>, <yukuai@...as.com>
Subject: Re: [PATCH v9 4/5] md: add check_new_feature module parameter
Hi,
在 2025/11/6 21:15, Xiao Ni 写道:
> In patch05, the commit says this:
>
> Future mdadm should support setting LBS via metadata field during RAID
> creation and the new sysfs. Though the kernel allows runtime LBS changes,
> users should avoid modifying it after creating partitions or filesystems
> to prevent compatibility issues.
>
> So it only can specify logical block size when creating an array. In
> the case you mentioned above, in step3, the array will be assembled in
> new kernel and the sb->pad3 will not be set, right?
No, lbs will be set to the value array actually use in metadata, otherwise
data loss problem will not be fixed for the array with different lbs from
underlying disks, this is what we want to fix in the first place.
Thanks,
Kuai
Powered by blists - more mailing lists