On Thu, Apr 18, 2024 at 09:42:06AM +0200, Hannes Reinecke wrote:
> While this can be fixed in userspace (Martin Wilck provided a patchset
> to multipath-tools), what I find irritating is that we will always
> display the max_sectors setting in kb, even if the actual value is not
> kb aligned.
The problem you are running into it exactly a problem of pointlessly
inheriting the value when we should not.
Other secondary issues are that we:
a) should allow the modification in the granularity that we actually
internally use, that is sectors
b) apparently some drivers still use the silly BLK_SAFE_MAX_SECTORS
limits that is too low for just about any modern hardwre.
>> Note that we really should not stack max_sectors anyway, as it's only
>> used for splitting in the lower device to start with.
>
> If that's the case, why don't we inhibit the modification for max_sectors
> on the lower devices?
Why would we? It makes absolutly no sense to inherit these limits,
the lower device will split anyway which is very much the point of
the immutable bio_vec work.
