Description of problem: Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.9-29.fc18.x86_64 How reproducible: Steps to Reproduce: 1. # multipath -t | grep -i daemon queue_without_daemon no 2. # multipath -q # echo $? 0 3. # multipath -t | grep -i daemon queue_without_daemon no Actual results: Expected results: should change the queue_without_daemon to 'yes' Additional info:
Created attachment 627171 [details] multipath.log
I think there is a misunderstanding of what "-q" does. It's not supposed to change the configuration, which is what you are checking with those commands. Normally, multipath won't set a device to queue at all if it's created when the daemon is not running. Not even queue_without_daemon will do that. It only keeps queueing enabled when the daemon stops. It's for things like restarting the daemon, where you don't want to lose your queueing in that window. In normal circumstances starting queueing without the daemon means that your device could get hung forever, since you can restore paths to the device without the daemon. If you know that the daemon will be starting shortly, using the -q option is O.K. this was necessary in the past. However it is not in recent releases, so this option is only there for historical reasons. It has no real use anymore.