Proxmox GUI Storage View Timeout (596) when listing VM Disks on NFS Storage

L

linuxxx3250

New Member
Nov 7, 2025
4
1
3
Hello Team,


We are experiencing an issue while browsing VM disks on NFS storage through the Proxmox GUI.

Environment​


Affected Versions:
  • Proxmox VE 8.4.0
  • Proxmox VE 9.2.2

Storage Type:
  • NFS Storage

    Issue Description : When navigating to "Datacenter ==> -> Storage ==> <NFS Storage> ==> VM Disks" and selecting a particular host's NFS storage, the GUI attempts to list the VM disks but eventually fails with the following error "Connection timed out (596)".
    Are there any known timeout limitations when the NFS datastore contains a large number of VM disks?

    Please help me to fix this issue.


  • pveversion -v
    proxmox-ve: 9.2.0 (running kernel: 7.0.2-6-pve)
    pve-manager: 9.2.2 (running version: 9.2.2/b9984c6d90a4bd80)
    proxmox-kernel-helper: 9.1.0+fde2
    proxmox-kernel-7.0: 7.0.2-6
    proxmox-kernel-7.0.2-6-pve-signed: 7.0.2-6
    ceph-fuse: 19.2.3-pve4
    corosync: 3.1.10-pve2
    criu: 4.1.1-1
    frr-pythontools: 10.6.1-1+pve2
    ifupdown2: 3.3.0-1+pmx12
    intel-microcode: 3.20251111.1~deb13u1
    ksm-control-daemon: 1.5-1
    libjs-extjs: 7.0.0-5
    libproxmox-acme-perl: 1.7.1
    libproxmox-backup-qemu0: 2.0.2
    libproxmox-rs-perl: 0.4.1
    libpve-access-control: 9.1.1
    libpve-apiclient-perl: 3.4.2
    libpve-cluster-api-perl: 9.1.5
    libpve-cluster-perl: 9.1.5
    libpve-common-perl: 9.1.12
    libpve-guest-common-perl: 6.0.3
    libpve-http-server-perl: 6.0.5
    libpve-network-perl: 1.6.5
    libpve-notify-perl: 9.1.5
    libpve-rs-perl: 0.15.3
    libpve-storage-perl: 9.1.5
    libspice-server1: 0.15.2-1+b1
    lvm2: 2.03.31-2+pmx1
    lxc-pve: 7.0.0-2
    lxcfs: 7.0.0-pve1
    novnc-pve: 1.7.0-1
    proxmox-backup-client: 4.2.0-1
    proxmox-backup-file-restore: 4.2.0-1
    proxmox-backup-restore-image: 1.0.0
    proxmox-firewall: 1.2.3
    proxmox-kernel-helper: 9.1.0+fde2
    proxmox-mail-forward: 1.0.3
    proxmox-mini-journalreader: 1.6
    proxmox-offline-mirror-helper: 0.7.4
    proxmox-widget-toolkit: 5.2.2
    pve-cluster: 9.1.5
    pve-container: 6.1.10
    pve-docs: 9.2.1
    pve-edk2-firmware: 4.2025.05-2
    pve-esxi-import-tools: 1.0.1
    pve-firewall: 6.0.4
    pve-firmware: 3.18-3
    pve-ha-manager: 5.2.4
    pve-i18n: 3.7.4
    pve-qemu-kvm: 11.0.0-3
    pve-xtermjs: 6.0.0-1
    qemu-server: 9.1.15
    smartmontools: 7.5-pve2
    spiceterm: 3.4.2
    swtpm: 0.8.0+pve3
    vncterm: 1.9.2
    zfsutils-linux: 2.4.2-pve1



  • pvesm status
    Name Type Status Total (KiB) Used (KiB) Available (KiB) %
    local dir active 98497780 4378212 89070020 4.44%
    local-lvm lvmthin active 335101952 0 335101952 0.00%
    local-nb_prod rbd active 6653900331 37266987 6616633344 0.56%
    nfs-prod nfs active 44961468608 37359865984 7601602624 83.09%
 

Attachments

  • Proxmox_GUI_Storage_View_Timeout_(596)_NFS_Storage.jpg
    Proxmox_GUI_Storage_View_Timeout_(596)_NFS_Storage.jpg
    20.2 KB · Views: 4
Hi @linuxxx3250 , welcome to the forum.

Have you checked the journalctl and dmesg on the PVE host at the time of errors?
In my experience not all NFS servers are created equal. Some struggle with directory listings when a lot of files are present, although that usually happens when are talking about tens of thousands to millions of files.
Another common reason for such issues are retransmissions. You should examine your network interfaces for errors. Check the MTU, etc.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
We never had timeouts for that listing You can even do
Code: 
ls -l /mnt/pve/<nfs-store-name>/images/*/*.*
and the result take just milliseconds for >180 vdisks (on 10x4TB hw-raid6-xfs-nfs4.2) - the gui takes 12s, so it's 99,9% working time in pve for the gui and that result time is the same on all of 5 cluster nodes - but in reality what is this kind of view use for ? MTU should stay default 1500 on all nics and switch ports to the storage.
 
Last edited:
@bbgeek17 & @waltar - Thanks for the reply.
I tested the NFS mount from the Proxmox host. The storage is mounted via NFSv3 over TCP with MTU 1500, and ip -s link does not show significant interface errors.
I also ran time ls -l /mnt/pve/nfs-prod/images/*/*.*, and the directory listing completed in about 1.2 seconds even with a large number of VM disks.
This suggests the NFS server and network are not the main bottleneck. The timeout appears to be in the Proxmox GUI/API path when building the “VM Disks” view, likely due to additional metadata processing or a request timeout
 
====================================================================================
ls -l /mnt/pve/nfs-prod/images/*/*.* | wc -l

820
====================================================================================


time find /mnt/pve/nfs-prod/images -type f | wc -l
820

real 0m1.018s
user 0m0.006s
sys 0m0.026s


=========================================================================================

ip -s link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped missed mcast
316026103958 105240924 0 0 0 0
TX: bytes packets errors dropped carrier collsns
316026103958 105240924 0 0 0 0
2: nic0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f0
altname enx8030e043b8d0
3: nic1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f1
altname enx8030e043b8d1
4: nic2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d2 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f2
altname enx8030e043b8d2
5: nic4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:ce:4d:60 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp18s0f0np0
altname enx48df37ce4d60
6: nic3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d3 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f3
altname enx8030e043b8d3
7: nic5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:ce:4d:68 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp18s0f1np1
altname enx48df37ce4d68
8: nic6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1398982228558 1501006455 1 5452 0 3162949
TX: bytes packets errors dropped carrier collsns
1646971184484 1583110532 0 1 0 0
altname enp93s0f0
altname enx48df377fe7b0
9: nic7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp93s0f1
altname enx48df377fe7b1
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1133772420973 708309426 0 63941 0 3159723
TX: bytes packets errors dropped carrier collsns
1540857698985 583751712 0 5 0 0
14: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether f6:01:21:7a:b7:27 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
695072837 2204886 0 2 0 0
TX: bytes packets errors dropped carrier collsns
11112894358 89404320 0 0 0 0
45: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 42:3f:a9:d2:eb:35 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
36623850204 16658174 0 2 0 0
TX: bytes packets errors dropped carrier collsns
51578316230 80067208 0 0 0 0
46: tap104i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether f2:72:04:47:f1:da brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1401656608 4966663 0 2 0 0
TX: bytes packets errors dropped carrier collsns
12652525897 65169874 0 3885 0 0
47: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether ea:c6:e8:80:bf:d5 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
2495828 41271 0 0 0 0
TX: bytes packets errors dropped carrier collsns
3631778059 59575541 0 0 0 0
50: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 3e:91:b1:02:bf:96 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
72124871 596441 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5710901325 1223911 0 5891 0 0
51: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 2a:21:57:ac:4b:ac brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
74852829 631602 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5714444233 1236003 0 589 0 0
52: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 36:98:15:e3:d0:a1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
70274074 615018 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5702614373 1140607 0 209 0 0
53: tap107i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:c2:04:02:6d:8d brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17308559 271348 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3476772562 427937 0 0 0 0
54: tap108i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 82:e5:34:fe:64:d7 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17514852 274062 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3476974310 432019 0 2871 0 0
55: tap109i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:fe:7c:47:7e:bd brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17318799 278171 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3473290735 438471 0 4905 0 0
56: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:47:18:37:da:8d brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
14771214 252403 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3301658456 393705 0 0 0 0
 
  • Like
Reactions: waltar
linuxxx3250 said:
====================================================================================
ls -l /mnt/pve/nfs-prod/images/*/*.* | wc -l

820
====================================================================================


time find /mnt/pve/nfs-prod/images -type f | wc -l
820

real 0m1.018s
user 0m0.006s
sys 0m0.026s


=========================================================================================

ip -s link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped missed mcast
316026103958 105240924 0 0 0 0
TX: bytes packets errors dropped carrier collsns
316026103958 105240924 0 0 0 0
2: nic0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f0
altname enx8030e043b8d0
3: nic1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f1
altname enx8030e043b8d1
4: nic2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d2 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f2
altname enx8030e043b8d2
5: nic4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:ce:4d:60 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp18s0f0np0
altname enx48df37ce4d60
6: nic3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 80:30:e0:43:b8:d3 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp2s0f3
altname enx8030e043b8d3
7: nic5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:ce:4d:68 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp18s0f1np1
altname enx48df37ce4d68
8: nic6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1398982228558 1501006455 1 5452 0 3162949
TX: bytes packets errors dropped carrier collsns
1646971184484 1583110532 0 1 0 0
altname enp93s0f0
altname enx48df377fe7b0
9: nic7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0
altname enp93s0f1
altname enx48df377fe7b1
10: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 48:df:37:7f:e7:b0 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1133772420973 708309426 0 63941 0 3159723
TX: bytes packets errors dropped carrier collsns
1540857698985 583751712 0 5 0 0
14: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether f6:01:21:7a:b7:27 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
695072837 2204886 0 2 0 0
TX: bytes packets errors dropped carrier collsns
11112894358 89404320 0 0 0 0
45: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 42:3f:a9:d2:eb:35 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
36623850204 16658174 0 2 0 0
TX: bytes packets errors dropped carrier collsns
51578316230 80067208 0 0 0 0
46: tap104i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether f2:72:04:47:f1:da brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
1401656608 4966663 0 2 0 0
TX: bytes packets errors dropped carrier collsns
12652525897 65169874 0 3885 0 0
47: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether ea:c6:e8:80:bf:d5 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
2495828 41271 0 0 0 0
TX: bytes packets errors dropped carrier collsns
3631778059 59575541 0 0 0 0
50: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 3e:91:b1:02:bf:96 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
72124871 596441 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5710901325 1223911 0 5891 0 0
51: tap105i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 2a:21:57:ac:4b:ac brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
74852829 631602 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5714444233 1236003 0 589 0 0
52: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 36:98:15:e3:d0:a1 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
70274074 615018 0 2 0 0
TX: bytes packets errors dropped carrier collsns
5702614373 1140607 0 209 0 0
53: tap107i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:c2:04:02:6d:8d brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17308559 271348 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3476772562 427937 0 0 0 0
54: tap108i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 82:e5:34:fe:64:d7 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17514852 274062 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3476974310 432019 0 2871 0 0
55: tap109i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 52:fe:7c:47:7e:bd brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
17318799 278171 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3473290735 438471 0 4905 0 0
56: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:47:18:37:da:8d brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
14771214 252403 0 2 0 0
TX: bytes packets errors dropped carrier collsns
3301658456 393705 0 0 0 0
Click to expand...
 

Attachments

Next steps are:
  • Execute pvesm list <storage>.
  • Examine your browser's developer tools to see whether a particular API call is hanging or taking an unusually long time.
  • Use pvesh to execute the relevant storage listing calls and determine where the delay is originating.
Please keep in mind that there are hundreds of thousands of PVE installations worldwide. While the number of disks you have is higher than what an average home user would have, it is not unusual for a business environment. We have customers with even larger numbers of virtual disks, although they are not hosted on NFS storage.

The point is that there is likely something specific to your environment that is contributing to the behavior you are seeing. It is certainly possible that you've uncovered an edge case or a bug in the code, but the next step is to narrow down where the delay originates. The more precisely you can identify the source, the easier it will be for the Proxmox developers to determine whether you're dealing with an environmental issue or a software bug.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: waltar
Just for comparison, any pvesh ls /nodes|/storage|/... takes 1 to 5 sec while any pvesm list <storage_name> took 30 to 32 sec on our 5 nodes which is 100x slower than the mentioned listing via shell ls -l /mnt/pve/<nfs-store-name>/images/*/*.*
 
If this was my environment and something I wanted to resolve, I would even try:
Creating a new storage pool, manually add disks to this pull (pvesm alloc) and test the response time until it exceeds reasonable time. Reduce the number of disks - does the response recover? Etc.

If this is something affecting production environment, you should have a support subscription that you can engage.

If its something you want to troubleshoot on your own : reduce the number of variables, find a reproducible scenario, provide useful debug information.

We have a saying : the most difficult part of storage is networking.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: waltar
You must log in or register to reply here.
Top Bottom
Back