Hey,
Thorsten was so kind to reach out and ask for help, this is a tricky situation.
The issue seems to be outlined, of bdev udev rules being greedy and grabbing all devices before multipath service kicks in.
Sadly there isn't a great proposal or solution yet.
Nor have I read about an easy way to reproduce.
Discussions seem to happen in MM ~maas-bcache-tools-jbod-multipath-bug but I haven't joined that yet.
In regard to testing I'd expect a modified variant of my multipath/tgt autopkgtest should work using iscsi to create multiple paths to the same disk - which we then can set up as bcache and check the behavior (without having full systems deployed via maas).
tagging it for server team to have a look but until there is a breakthrough to find an approach I'm unsure about progress expectations.
Hey,
Thorsten was so kind to reach out and ask for help, this is a tricky situation.
The issue seems to be outlined, of bdev udev rules being greedy and grabbing all devices before multipath service kicks in.
Sadly there isn't a great proposal or solution yet.
Nor have I read about an easy way to reproduce.
Discussions seem to happen in MM ~maas-bcache- tools-jbod- multipath- bug but I haven't joined that yet.
In regard to testing I'd expect a modified variant of my multipath/tgt autopkgtest should work using iscsi to create multiple paths to the same disk - which we then can set up as bcache and check the behavior (without having full systems deployed via maas).
tagging it for server team to have a look but until there is a breakthrough to find an approach I'm unsure about progress expectations.