tapdisks with wrong port and protocol seem to hang

[kinvaris]

Used a wrong protocol and wrong port:

root@cmp04:~# tap-ctl create -a openvstorage+tcp:172.22.1.30:26201/fio1
^C
root@cmp04:~# 
root@cmp04:~# 
root@cmp04:~# 
root@cmp04:~# tap-ctl list
^C

The correct port here is 26203 and protocol is RDMA...

Seen that the tap-ctl list commands times out after 2 minutes:

root@cmp04:~# ps -ef | grep tap
root      1528     1  0 14:54 ?        00:00:00 tapdisk
root      2941     1  0 14:56 ?        00:00:00 tapdisk
root      2959     1  0 14:56 ?        00:00:00 tapdisk
root      3035     1  0 14:56 ?        00:00:00 tapdisk
root      3051     1  0 14:56 ?        00:00:00 tapdisk
root      3066     1  0 14:56 ?        00:00:00 tapdisk
root      3142     1  0 14:56 ?        00:00:00 tapdisk
root      3157     1  0 14:56 ?        00:00:00 tapdisk
root     23191     1  0 15:21 ?        00:00:00 tapdisk
root     23256 18100  0 15:21 pts/33   00:00:00 tap-ctl list
root     24559 23868  0 15:23 pts/14   00:00:00 grep --color=auto tap

But this disk: root 23191 1 0 15:21 ? 00:00:00 tapdisk kept hanging. This also meant that the tap-ctl list command was useless

After killing the process. The command worked again.

[cnanakos]

The port provided here has an already binded server (XML-RPC), tapdisk is connecting but cannot open the provided volume, thus the process hangs there.