Aha, good thinking about reproducing with virsh. To find out what virt-manager is doing, I did:
LIBVIRT_DEBUG=1 virt-manager --no-fork
Clicking the refresh button shows me it's doing "virStoragePoolRefresh", which takes me to ftp://libvirt.org/libvirt/virshcmdref/html/sect-pool-refresh.html
And yes, I can reproduce using just virsh pool-refresh:
root@beaver:~# virsh vol-create-as --pool zfs --name vol1 --capacity 1G Vol vol1 created
root@beaver:~# virsh vol-list --pool zfs Name Path ------------------------------------------------------------------------------ vol1 /dev/zvol/zfs/images/vol1
root@beaver:~# virsh pool-refresh zfs Pool zfs refreshed
root@beaver:~# virsh vol-list --pool zfs Name Path ------------------------------------------------------------------------------
root@beaver:~#
Aha, good thinking about reproducing with virsh. To find out what virt-manager is doing, I did:
LIBVIRT_DEBUG=1 virt-manager --no-fork
Clicking the refresh button shows me it's doing "virStoragePool Refresh" , which takes me to org/libvirt/ virshcmdref/ html/sect- pool-refresh. html
ftp://libvirt.
And yes, I can reproduce using just virsh pool-refresh:
root@beaver:~# virsh vol-create-as --pool zfs --name vol1 --capacity 1G
Vol vol1 created
root@beaver:~# virsh vol-list --pool zfs ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- - zfs/images/ vol1
Name Path
-------
vol1 /dev/zvol/
root@beaver:~# virsh pool-refresh zfs
Pool zfs refreshed
root@beaver:~# virsh vol-list --pool zfs ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -
Name Path
-------
root@beaver:~#