aoe block device remains after torusblk process finished

[nak3]

version

a9c6bc183143c2f2780bd999dd47ae152c4f4757 (+ aoe readystatus issue fix)

issue

• torusblk aoe <VOL_NAME> lo 1 1 creates block device under /dev/etherd/e.1.1. The torusblk process finished, the device still remains and fdisk -l hang.
• And also, shutdown process would be hung.

steps to reproduce

1. Run torusblk aoe and finished the process.

$ torusblk aoe <VOL_NAME> lo 1 1

.. Ctrl+C ..

2 Confirm under blcok device e1.1 under /dev/etherd

# cd /dev/etherd
# ls
discover  e1.1  err  flush  interfaces  revalidate

3. Run fdisk

# fdisk -l
Disk /dev/vda: 41 GiB, 44023414784 bytes, 85983232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x38df41da

...

Disk /dev/mapper/docker-252:1-1572957-pool: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

  -- It hang here --

additional info

aoe-flush from aoe-tools can solve the hunging.

# cd /dev/etherd/
# aoe-flush e1.1

Torus should clean up the block device when the torusblk process finished. Or provide the tool like aoe-flush.