From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 7C15EA052C for ; Tue, 13 Jun 2023 10:36:04 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6320C2C160 for ; Tue, 13 Jun 2023 10:36:04 +0200 (CEST) Received: from mx1.ovgu.de (mx1.ovgu.de [141.44.1.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 13 Jun 2023 10:36:03 +0200 (CEST) Received: from exchange.ovgu.de (pwedge03.ads.uni-magdeburg.de [141.44.16.177]) by mx1.ovgu.de (Postfix) with ESMTPS id C91875E059A for ; Tue, 13 Jun 2023 08:30:52 +0000 (UTC) Received: from pwedge04.ads.uni-magdeburg.de (141.44.16.180) by pwedge03.ads.uni-magdeburg.de (141.44.16.177) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.12; Tue, 13 Jun 2023 10:30:53 +0200 Received: from pwedge04.ads.uni-magdeburg.de ([fe80::e6b0:1262:982d:b593]) by pwedge04.ads.uni-magdeburg.de ([fe80::e6b0:1262:982d:b593%11]) with mapi id 15.02.1258.012; Tue, 13 Jun 2023 10:30:53 +0200 From: "Naumann, Thomas" To: "pve-user@lists.proxmox.com" Thread-Topic: Limitation File Restore List Thread-Index: AQHZndFdJ7xw4OLdzk64yMhlNGb8fA== Date: Tue, 13 Jun 2023 08:30:52 +0000 Message-ID: <49ddc1dbfa93638026bac9a89dda78da3a8f99c6.camel@ovgu.de> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [141.44.13.75] Content-Type: multipart/signed; micalg=sha-256; protocol="application/pkcs7-signature"; boundary="=-fm33MlVagDXE4oGscH0N" MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.192 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] Limitation File Restore List X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2023 08:36:04 -0000 --=-fm33MlVagDXE4oGscH0N Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi at all, following general conditions are given: - 12 node Proxmox-Cluster (48 x Intel(R) Xeon(R) CPU E5-2690 v3 / 256 GB RAM) - 96 Osd Ceph-Pool -> 6x HDD / TOSHIBA_MG07ACA14TE + 2x SSD / SAMSUNG_MZILT7T6HALA_007 (Ceph-DB) per node - 10 GBit Network - 10 PBS VMs running - 1 PBS VM (55 GB RAM, 16 CPUs, 35 TB Backup-Datastore XFS) Last mentioned PBS VM ist connected with another Proxmox-Cluster (9 nodes 24 x Intel(R) Xeon(R) CPU X5670, 142 GB RAM, 56 SSD OSDs, 30 VMs running) as Backup-Storage for VMs. 1 VM running on this cluster (32 GB RAM, 16 CPUs, 12 TB HDD (virtio, discard, iothread), OpenSuse Leap 15.4) is mailserver. 12 TB HDD has one directory "MAIL" with 23000 subdirectories (1 subdir per user), 10 TB are in use. PBS-client per CLI is working without any problems - for example: mapping PBS-snapshot and listing subdirs in MAIL-directory. Listening / viewing subdirectories of MAIL-dir per Web-GUI (VM -> Backup -> File Restore -> click "+" of MAIL-dir) is not working. After waiting for about 4-5 minutes error code "list not finished in time (503)" appears. Logfiles (/var/log/proxmox-backup/file-restore/qemu.log + journalctl) do not show anything "unnormal" or error related. What exactly is the root cause of this behaviour and how to solve this? Any hint / thought is welcome / helpful.... best regards Th. Naumann --=-fm33MlVagDXE4oGscH0N--