That's never how it works. multipath has no kernel module loading ability. Would
make a nice feature though. I admit that discovering "which dh
is the necessary one" is a bit arcane and not well documented anywhere.
The best practice here is to load the necessary device handler into your initrd so
it's attached at the same time the SD devices are initially discovered. You still
need to have this module loaded to provision additional luns at runtime and
not have their performance plummet.
Also, I discovered a typo in the multipath documentation.
That's never how it works. multipath has no kernel module loading ability. Would
make a nice feature though. I admit that discovering "which dh
is the necessary one" is a bit arcane and not well documented anywhere.
The best practice here is to load the necessary device handler into your initrd so
it's attached at the same time the SD devices are initially discovered. You still
need to have this module loaded to provision additional luns at runtime and
not have their performance plummet.
Also, I discovered a typo in the multipath documentation.
https:/ /bugs.launchpad .net/serverguid e/+bug/ 1057071
Had that worked to begin with, you would have never encountered this
issue in the first place.
Closing this issue as "Invalid" as it's not a bug. Thanks for the report.