nvme: problem with chunk_sectors and blkzone

[Javier González]

OK, ignore this. I was in a mid-version from October where I was getting
chunk_sectors to be 0. Just pulled and it is OK.

Sorry for the noise.

Javier

On 06.11.2020 13:34, Javier González wrote:
>Keith,
>
>I have noticed that one of the patches merged some time ago, where we
>are avoiding to set chunk_sectors due to the lack of noiob indirectly
>breaks blkzone
>
>   e83d776f9f98b nvme: only use power of two io boundaries
>
>if id->noiob is not set, then chunk_sectors is set to 0, which turns out
>in blkzone failing in ZNS SSDs not setting the IO boundary
>
>    blkzone: /dev/nvme0n1: unable to determine zone size
>
>This is easy reproduceable with QEMU
>
>Am I missing something here?
>
>I am happy to send a patch to utils-linux fixing this (have one with me
>as I looked into the problem), but I think it is worth reporting this as
>it is effectively breaking user-space.
>
>Thoughts?
>
>Javier