On Wed, Apr 13, 2022 at 11:02:47AM +0800, Yi Zhang wrote: > On Wed, Apr 13, 2022 at 8:24 AM Luis Chamberlain <mcgrof@xxxxxxxxxx> wrote: > > > > I do have CONFIG_NVME_MULTIPATH=y but I also have: > > > > cat /etc/modprobe.d/nvme.conf > > options nvme_core multipath=N > > > > And yet I always end up booting with: > > > > cat /sys/module/nvme_core/parameters/multipath > > Y > > > > So trying to run: > > > > nvme_trtype=rdma ./check nvmeof-mp > > > > I end up with the warning: > > > > nvmeof-mp/*** [not run] > > CONFIG_NVME_MULTIPATH has been set in .config and multipathing has been enabled in the nvme_core kernel module > > > > Are there times where one cannot disable multipath? I'm not using > > any nvme drive at boot, but I do use one for a random data parition. > > So the multipath is not updated with N, pls try manually removing the > nvme_core module and retest. I can't remove the module as a filesystem is mounted on one of the nvme drives used at boot. It is not an OS partition, ie, it is just /data/. The blktests is intended for some other nvme drives. > Or just reboot can also help update the parameter. Reboot does not help, that is my point. > BTW, to run blktests nvmeof-mp, the correct way is: > # ./check nvmeof-mp > # use_siw=1 ./check nvmeof-mp That does not let me do anything different as CONFIG_NVME_MULTIPATH is still found to be set and the module parameter for nvme_core for multipath is still "Y". Luis
